[AccessD] Access Lock File problem

Jim Dettman jimdettman at verizon.net
Wed May 27 13:04:10 CDT 2009


Janet,

<<is there some setting I'm missing in Access that's causing this issue?>>

  What you need to get to the bottom to is why the .LDB is left behind.
Under normal circumstances, the .LDB file should be getting deleted once the
last person has left the DB.

  Either the user in question doesn't have delete privs for the directory
where the DB resides, the compact/repair is not completing successfully, or
they are terminating the process in some way abnormally.

<<Is there some other way I can release the ldb file without having to
re-boot?>>
  
  Drew posted the one method that covers things about 90% of the time, but
it will not show the open file if a local process is accessing the file.  To
check the local server, you need to use something like process explorer,
which will let you check all the open file handles.

http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

Jim.  

 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Janet Erbach
Sent: Wednesday, May 27, 2009 12:25 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Access Lock File problem

Dear Forum Folks:

We have an access order management application here that has a front-end
installed on 10 computers and a back-end that resides on the server.  We
compact/backup the back-end mdb every day - usually with no problem.  But
the compact/back-end, of course requires that only ONE computer can be
accessing the back-end mdb, and every once in awhile the person running the
compact forgets to close out the app on one of the computers.  When that
happens it seems like the lock file gets 'locked' for good;  even after
making sure EVERYONE is out of the app, access thinks the mdb is locked.

The only solution I've found so far is to re-boot the server and then delete
the lock file.  This seems like an in-elegant and time-wasting solution to
me;  is there some setting I'm missing in Access that's causing this issue?
Is there some other way I can release the ldb file without having to
re-boot?

Thanks!

Janet Erbach
IT Prognosticator
Natural Healthy Concepts
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list