In addition to create & delete privileges, all users must have read & write privileges as well.
I recommend using Notepad, from each users workstation logged on as that user, to verify RWCD
privileges. Don't just depend on some system administrator telling you that they set it up
correctly for all users. Test it out for yourself.
Additional information is available here:
Introduction to .ldb files
http://support.microsoft.com/?id=299373
Tom
____________________________
A simple Access app issues a message: "Database has been placed in a
state by Admin on machine XXXX that prevents it from being opened or
locked" sometimes this comes up and no new users can open the
database, other times everybody can open the database fine.
Any ideas ?
TIA,
Charlie
Often this is the result of Access rights to the directory where the
Access file is stored. It can also happen when someone turns their computer
with Access still logged on the back end copy.
There is a LDB file that is created when someone opens the back end
database or links to it. This file keeps track of who is logged on and what
changes they are making . The individual needs to have the rights to create
and delete files in that directory. If you know everyone is logged out, you
should be able to manually delete the "YOURFILENAME.LDB" file manually,
assuming you have access rights to that directory that allow you to delete
files.
--
Joseph Meehan
26 + 6 = 1 It's Irish Math
____________________________
A simple Access app issues a message: "Database has been placed in a state by
Admin on machine XXXX that prevents it from being opened or locked" sometimes
this comes up and no new users can open the database, other times everybody
can open the database fine.
Any ideas ?
TIA,
Charlie
