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!
Record Lock on Database will not go away
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.
How do I find out who has it locked.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
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.
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.
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.
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.
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.
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.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial