By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,222 Members | 1,123 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,222 IT Pros & Developers. It's quick & easy.

Access.LockFile.9 problem

P: 97
Hi,

My access db (linked to MySQL) is generating an error out saying that another user has the database in exclusive mode. No one else is on the system.

How can I get rid of the problem? I tried to delete the ldb (Access.LockFile9), but unable to do that.

Thanks in advance.
Jan 11 '08 #1
Share this Question
Share on Google+
4 Replies


puppydogbuddy
Expert 100+
P: 1,923
Hi,

My access db (linked to MySQL) is generating an error out saying that another user has the database in exclusive mode. No one else is on the system.

How can I get rid of the problem? I tried to delete the ldb (Access.LockFile9), but unable to do that.

Thanks in advance.
Hi Again,
You can delete the .ldb file after shutting down and restarting your server without starting the application. Of greater concern is what caused the lock in the first place because frequent locking can be a symptom of, or can cause corruption.

The lock can be caused by incomplete/poor coding practices. An example include recordset processing code that closes the Recordset object, but does not close the database object and/or the connection object.
Jan 11 '08 #2

P: 97
Hi Again,
You can delete the .ldb file after shutting down and restarting your server without starting the application. Of greater concern is what caused the lock in the first place because frequent locking can be a symptom of, or can cause corruption.

The lock can be caused by incomplete/poor coding practices. An example include recordset processing code that closes the Recordset object, but does not close the database object and/or the connection object.
Hi, puppydogbuddy again!
I had opened the access db on the server to work, and also on another terminal to test as a user. I was working on debugging the CDate problem error on my server while I was testing it on the user's computer. On the user's computer, it kept generating backup file and backup_backup file, and so on. I did close the db on the server and tried to reopen it, but it won't open. It errors out of that I am not accessing exclusively.... and the .ldb file had unknown system icon and stayed after the db closed. I was curiouse so I open the .ldb file in notepad, from then .ldb file keeps showing notepad/text icon. My apology for not explaining concisely and clearly, but I am a bit confused by now.
Jan 11 '08 #3

puppydogbuddy
Expert 100+
P: 1,923
Hi, puppydogbuddy again!
I had opened the access db on the server to work, and also on another terminal to test as a user. I was working on debugging the CDate problem error on my server while I was testing it on the user's computer. On the user's computer, it kept generating backup file and backup_backup file, and so on. I did close the db on the server and tried to reopen it, but it won't open. It errors out of that I am not accessing exclusively.... and the .ldb file had unknown system icon and stayed after the db closed. I was curiouse so I open the .ldb file in notepad, from then .ldb file keeps showing notepad/text icon. My apology for not explaining concisely and clearly, but I am a bit confused by now.
So, you opened the db and did coding changes (considered to be a design change), which triggers Access to lock the db because design changes can only be done in exclusive (vs shared) mode.

Do you have the necessary permissions to delete files on the server? You may have to get your system db admin to do the file delete. If you have or get the necessary permissions to delete and you still can not delete the .ldb file after you shut down the db, then you may have to shut down and restart the network.
Jan 11 '08 #4

P: 97
So, you opened the db and did coding changes (considered to be a design change), which triggers Access to lock the db because design changes can only be done in exclusive (vs shared) mode.

Do you have the necessary permissions to delete files on the server? You may have to get your system db admin to do the file delete. If you have or get the necessary permissions to delete and you still can not delete the .ldb file after you shut down the db, then you may have to shut down and restart the network.
Thank you so much!
I shut and restarted my server and I was able to delete the .ldb file. Thanks again!
Jan 11 '08 #5

Post your reply

Sign in to post your reply or Sign up for a free account.