How do I find who is locking the database?

wanluo

New member
Local time
Today, 15:34
Joined
Nov 13, 2007
Messages
3
Have an Access database that is used by multiple users, the lock file seems to have vanished. Yet the database is in a read only state and still locked. How do I unlock the database? How do I find out who is locking it? How do I kick the person off is neccesary to unlock the database? Thanks.
 
Well I'm a little confused, if there is no lock file then the database isn't locked in the traditional sense. If it is coming up as read only check the file properties and make sure someone didn't set the Read Only file property to true. Microsoft also has a free download called LDBview.exe which will let you view the users in the ldb file, you can get the users PC name this way. There really isn't a way to kick them out unless you have a hidden form running in the background which could do that, check the forum for examples of that.

If this is on a network drive try copying the file offline, doing a compact repair, then replacing the network copy with the compacted one.
 
Have an Access database that is used by multiple users, the lock file seems to have vanished. Yet the database is in a read only state and still locked. How do I unlock the database? How do I find out who is locking it? How do I kick the person off is neccesary to unlock the database? Thanks.

Hi

Please find attached the WhosOn2000 utility that will show you who has the database open.

As mentioned, if there is no lock file, the the database is not locked

What is your config? FE/BE

Best regards

Maurice
 

Attachments

Check all thathas been suggested but alsocheck the network permissions.

Do the users have a full set of permissions at network level to Read, Write, Modify and Delete.

Just wondering if there is a locking process occurring inside the database that cannotbe written to the ldb and therefore not released because the abscence of the ldb
I get very nervous when a full set of network permissions are not assigned and have had a few arguments about it here.

I won cos I said either full set or you sort any problems

I control who can do what inside the application

You can also read the ldb with Notepad

L
 
The FE was locked. Many users have full control to the directory. Had the network admin kick everyone from the directory, that seems to have release the db but still not sure what cause the problem and a solution to it. Thanks.
 
Be aware that you should allow separate copies of the FE to prevent locks.

Also, if the database folder doesn't allow CREATE permissions, you cannot CREATE the LDB file. If you cannot create the LDB then the DB is effectively locked to READ-ONLY mode.
 

Users who are viewing this thread

Back
Top Bottom