[AccessD] Access Lock File problem

One cautionary note on this method: 

I have ran into this situation a few times and if the Access FE is bound to
the Access BE cutting the connection can result data corruption. I have had
a couple of rather serious results when working with MDBs for government
agencies.

My recommendation is the either build an application without bound
connections or use a more robust DB like MS SQL/Oracle/MySQL etc.

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Wednesday, May 27, 2009 9:55 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Access Lock File problem

Right click on My Computer on the server.  Select 'Manage'.  Under
'Shared Folders' you'll find 'Open Files'. This will show all the
'locked/open' files on the server, and you can right click on the
entries and force them closed.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Janet Erbach
Sent: Wednesday, May 27, 2009 11:25 AM
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
The information contained in this transmission is intended only for the
person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI
Business 
Sensitive material. If you are not the intended recipient, please contact
the sender 
immediately and destroy the material in its entirety, whether electronic or
hard copy. 
You are notified that any review, retransmission, copying, disclosure,
dissemination, 
or other use of, or taking of any action in reliance upon this information
by persons 
or entities other than the intended recipient is prohibited.


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com