secure db @ login: could not save; currently locked by another us.

[Guest]

We are in the process of updating our PCs from Windows 2002 to XP
Professional.
On four of the 20 updated PCs, when a user tries to open the db, the message
"could not save: currently locked by another user" pops up. The message is
PC specific and the db can not be opened by that PC until all other users
close the db. Any ideas on a setting that might need to be changed on those
four PCs? Tools, Options, Advance is set to "No Locked Records" in the db.
It seems a setting on the individual PCs needs to be changed.

Thanks for anything you can suggest to eliminate the problem.

Michelle

 

[Ron Hinds]

We are in the process of updating our PCs from Windows 2002 to XP
Professional.
On four of the 20 updated PCs, when a user tries to open the db, the
message
"could not save: currently locked by another user" pops up. The message
is
PC specific and the db can not be opened by that PC until all other users
close the db. Any ideas on a setting that might need to be changed on
those
four PCs? Tools, Options, Advance is set to "No Locked Records" in the
db.
It seems a setting on the individual PCs needs to be changed.

Thanks for anything you can suggest to eliminate the problem.

Michelle

It sounds like a NTFS permissions problem. Access tries to create a .LDB
(Database Locking File) when multiple users are in the db. Is the
application a split db? Do those users have the Modify, Read, and Write
permissions in the shared folder where the backend db is? Try to just create
a new text file in that folder when logged on as one of those users from one
of those PCs. If you can't, you need to look at the permissions.