Record Lock on Database will not go away

seamus9909
seamus9909 used Ask the Experts™
on
I have a Backend Access Data Base, that has an associated Record Lock File, yet noone is logged into the database.  Every time I try to delete it it says another user has the DB. However I do not see who that person is.

How do I find out who has it locked.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2017
Commented:
Sometimes, when you are sure that everyone is really out of the database, if you open it and close it, Access will naturally delete the lock file - assuming that the person opening/closing has delete permission to the folder holding the database.  Remember, all users require Creat, Read, Update, Delete permission to the folder because the first person to open the file causes Access to CREATE the lock file and the last person to close the app causes Access to DELETE the lock file.  In between, everyone needs to have permission to read and update so Access can properly track actions in the lock file.

If nothing else works, you may have to reboot the server where the lock file persists in order to convince DOS to let it go.

Author

Commented:
i have rebooted the server and still it shows being locked?
John TsioumprisSoftware & Systems Engineer

Commented:
Check your antivirus on both your machine and server....disable them and try again...
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Distinguished Expert 2017

Commented:
Did you try deleting the lock file after the reboot?  Rebooting won't delete the file but it should kill what ever process was locking it.

Author

Commented:
Hi Yes i did try and delete it after reboot

Author

Commented:
Thank you that worked
Distinguished Expert 2017

Commented:
It's a little pesky and most network admins are loath to reboot a server if they don't have to.  You just have to convince them to do it but in your case, you were lucky enough to have the power to do it yourself.

Author

Commented:
Yes  now on to my bigger issues
Jim Dettman (EE MVE)President / Owner
Most Valuable Expert 2017
Most Valuable Expert 2012

Commented:
Couple other comments:

1. A LDB will also get left behind if a user abnormally disconnects from the DB.  As Pat said, all users should have delete priv's.   Check this and then if the LDB continues to get left behind, you've got other issues.

2. It is possible to release the lock on the LDB without rebooting the server.   If it's a network connection, you just have to close the session.  That's done from Computer Managernt, Files and Shares.

  If the lock is from a local logon, then you would need to use something like process Explorer that can find the handle and kill it.

Jim.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial