Can’t remove the lock file!

[Mats B]

I have a built a database application with a front end and a back end
database. It works fine but sometimes, after closing the application, the
lock file isn’t removed. The database thinks I’m still logged on even if I’m
not.

Why isn’t the database considering me as logged on, even if I have closed
the database?
Is there any simple ways to reset the database if this occur, without
restarting the server?

 

[bob]

which LDB file does not close: the front-end or the back-end?

Can the LDB file be deleted? If not, that means something else is REALLY
using it!

Sometimes the Access front-end will appear to be closed but won't be: using
CTRL+ALT+DEL, look for MSACCESS.EXE in PROCESSES. If present, use End
process to close it.

If none of this helps, let me know: there are other things to do.

Bob

 

[Bill Mosca]

Your network guy can force the LDB to close. He should know how to do a
force. I don't have that information, but my network guy gave me an MSC
utility so I could do it. He should also force the databasse to close as well.

Once that's done, delete the LDB and compact your database.

A hanging LDB happens when you have a multi-user MDB and someone either uses
Ctrl+Alt+Del to close Access or undocks a laptop from the network or loses a
wireless connection. There are probably more ways to cause it, but those are
the ones I am aware of.

To prevent it from driving you crazy, split the database and give each user
a front end on his hard drive. as soon as I did that my hanging LDB
completely stopped showing up.