User cannot open one form, other users can

[Wayne West]

This is kinda strange. Access XP database, it's been split and linked into a
front-end with all of the forms and reports and a back-end with all the data.
The links are through explicit drive letter/directory pathing, not UNC
names. Multiple people are using this. And there's no security coded in the
system.

I have two users who cannot access one form in the system and also cannot
access most, if not all, reports. All of the other users, as far as I know,
have no problems accessing anything. I've repaired the thing, I've restored
it from a previous backup. Still no joy.

(I'm new to this job and don't have network admin access, just SQL DBA admin
access, which kinda hampers my troubleshooting. I'm moderately skilled in
Access, though very rusty.)

The problem is not machine-specific as the user can log on to her PC as
someone else and has access to the one form and all reports. Which leads me
to believe that it is profile or permissions specific. I don't think it can
be permissions specific as network permissions apply to the file level, they
shouldn't affect anything within the MDB. The help desk guys say that they
have deleted the user's profile from her PC and recreated it, yet the problem
persists.

Any suggestions?

 

[Jerry Whittle]

1. Do all users have full permission to the folder holding the mdb files? Not
just the files themselves; rather the entire folder?

2. Are users hitting the same FE or do they each have their own FE? The
correct answer is that the each have their own FE located on their computer.

3. Double, no triple, check that they are hitting the correct FE and BE
files. Maybe they have a shortcut pointed to an older version of the FE or
the table links are to a different version of the BE.

 

[Wayne West]

1. Yes, to the best of my knowledge.

2. See #1. They have desktop shortcuts to the FE.

3. There are no older copies of either file.

And I was able to open the table that the form is linked to.

 

[Wayne West]

OK, I quit.

It is now fixed, and you're not going to believe the resolution.

It was a corrupt printer driver.

I have no idea how the guy who developed it diagnosed it, but he came out
Friday and determined this, this AM the user had our help desk uninstall and
reinstall the printer driver, and now it works.

I give up. ;-)

 

[Todos Menos [MSFT]]

yeah I ran into that bug once... it took me FOREVER to diagnose this

it wasn't a 'corrupt' printer driver.
it was just an abnormal printer driver

I tell you-- Access Data Projects aren't as picky as MDB