Previously Shared MDB File Now Only Allows Single Users

[P Scarpelli]

An mdb file we have been using between 3 or 4 users with sharing options is
now only allowing one-at-a-time user to access the file
(Tools>Options>Advanced tab = Shared & No locks). When a second user tries
to open the mdb file, they get the message "Could not use 'file path and
name.mdb'; file already in use." I successfully ran a Compact & Repair but
this did not clear the issue. I noticed the .ldb file is hanging out there
even though no users have the file open. I'm thinking there is a problem
with this file. The Created, Modified, and Accessed dates with this file are
all Friday, September 05, 2008. Today is Tuesday, September 9, and there has
been activity associated with the associated mdb file today and yesterday.
Can anyone explain what is causing the lockout condition or offer a way to
get arround this problem? Also, I have tried to delete, rename, and move the
..ldb file but access is denied for me even though I have full permissions in
the file's folder.

 

[Klatuu]

Try deleting the ldb file.
It may be corrupt or, if the user rights for the folder where the mdb and
ldb files are has changed, it could cause that.

The ldb file is the "locking" file. For an mdb to be used by multiple
users, the users have to have read, write, and delete permissions to the
folder.

 

[John Spencer]

Try rebooting the computer that has the lock file (ldb) on it. Make sure no
one is logged into the database.

Once you do that immediately open the folder with the lockfile (ldb file) and
try deleting the lockfile.

John Spencer
Access MVP 2002-2005, 2007-2008
The Hilltop Institute
University of Maryland Baltimore County

 

[P Scarpelli]

As I mentioned in my original posting, I was unable to delete, rename, or
move the ldb file. When trying to delete the file I get the "Access is
Denied" message along with information to have me check to make sure the disk
is not full or write-protected. This seems somewhat bogus considering I and
others are able to delete other files as needed. I agree with you that this
ldb file may be corrupt. It would be helpful if there was a way to tell
which user it "thinks" is locking up the file/record.