Record Locking

[SylvieB]

Hi
I put my database on a shared drive on the network. Only one user at a time
can access it which is a problem. Multiple users should be able to open the
database at once. I checked the settings on my database under Tools, Advanced
tab, under default record locking: no locks and Open databases using record
level locking is unchecked.
I noticed that there is a ldb file in the same folder that the database.
What options or what can be done for multiple users to access the database
at once? In advance, thank you for any help you can offer.

 

[Stockwell43]

Hi Sylvie,

The ldb file is just telling you that you have your database opened. If your
users are trying to click on the ldb file to access the database, it won't
work. They should all be able to open it using the .mdb file.

 

[SylvieB]

Thanks for your quick answer. Yes, i understand that. All I want is for
multiple users to be able to access the database at the same time. Right now,
only one user can open the database. What needs to be done for more than one
user to open the database? Thanks

 

[Tom Wickerath]

Hi Sylvie,

All users should have RWCD (Read, Write, Create & Delete) privileges for the
shared folder, in order for the locking database file to work as designed. If
one or more users does not have create rights, and if they are the first one
to open your database, they will open it in exclusive mode, because the
system was unable to create a .ldb file for this user. More information here:

Introduction to .ldb Files
http://support.microsoft.com/?id=299373

With all users out of the database (ie. Access closed on all machines), make
sure that the locking database file that you did see gets deleted
automatically. All users should have delete rights on the folder, so that the
last user out causes the .ldb file to be deleted. Inspect the folder with
Windows Explorer. If you see a .ldb file hanging around, then try deleting
it. If all users are actually out of the database, you shouldn't see such a
file to start with.

It sounds to me like you may not have split your application into two
databases. These are commonly known as a "Front-end" (FE) application file,
and the "Back-end" (BE) data file. The FE contains all queries, forms,
reports, macros, modules and any local (unshared) tables. The BE database
contains the tables only with the shared data. Only the BE .mdb should be
shared. A copy of the FE should be installed on each user's local hard drive.

Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Stockwell43]

Do you have this in a secured folder on the network? If you did not assign
any security within the database, everyone should be able to get in just
fine. However, if the folder you placed the database in has level security,
you might need to check that. I would contact your IT deparment and make sure
this folder has no restriction that would limit the access to the database.
Is there another folder that everyone can access a database from? If so, try
copying and pasting your database in there and see what happens. If everyone
can access it, then it is a folder issue. If your having the same problem
then it's a database issue.

On a last ditch effort, try to create a blank database and import everything
from the database you are having a problem with (after you have already made
a copy of it) and see what happens. Sometimes you may have clicked something
without knowing it that triggered something else. By importing, it's like
refreshing the database sort of speak. I had to do it a couple of times
myself and it seemed to work. Just a thought if all else fails.