"Could Not Lock File"

[FedBrad]

I have read all the related posts (and links) that I have found here thus
far, but think my issue may have a slightly different twist.

We're running an .mdb on a network, multi-users (no security scheme), user
groups are used to control access to the folder and the actual file. Two
users within the same 'group' are not able to access this particular mdb at
the same time - i.e., anyone after the first user to open gets the same
message.

But here is the twist... If I test this with any other member of the same
group, we get the error. However, if I test with one of our IT folks, we can
both get in. IT is obviously not within the same user group. I have rights
at the folder level that are different (less restrictive) than my rights as a
member of the user group, but my rights at the file level are simply as a
member of the group. But, we have also confirmed that my rights at the
folder level are not being inherited at the file level.

Although we have checked and re-checked rights, we can't seem to solve this.
The same user group has no problems accessing any of the various other Dbs
that reside within the same folder, and the db settings are identical (i.e.,
Options, Advanced, Shared, No Locks, etc...). The only significant
difference is that this is the only db that is not split.

What might I be missing here? Thanks in advance...

 

[Allen Browne]

Could be rights to the folder.

When the first user opens a database in shared mode, Access creates a
locking file (.LDB) in the folder. When the last user logs out, it deletes
the LDB file. If the user cannot create the LDB, the database is opened
exclusively.

All users need full rights to the folder (including create and delete.)

 

[FedBrad]

Thanks Allen... I spend a lot of time here, and always respect (and often
look for) your responses to Access questions.

Seems everything I've seen points (mostly) to the rights issue - which was
the first question I posed to our network admin folks when the issue arose.
Thus far, I have relied on IT to ensure the rights are correct, perhaps it is
time to look over their shoulder...?

Brad