You should open the task manager (CTRL+ALT+DEL) and kill any running MSAccess.EXE processes left running then you should be able to delete the locking file.
Cheers,
Yes, that was my first thought, but there are no access tasks running when viewed in the Task Mgr
I had this problem in a NAS network. Network admin tweaked some sort of setting - seems that inactive files were not being purged expediently. He had the power to delete such files though. When he did I said "Thanks. I'll just call you when it happens again." That's all the incentive he needed to fix the problem. Perhaps the root cause is why the Access db is not being terminated properly by somebody.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
Please use # icon on toolbar when posting code snippets.
Cross Posting: https://www.excelguru.ca/content.php?184
Debugging Access: https://www.youtube.com/results?sear...bug+access+vba
If my error handlers can't dynamically fix a sever error, after displaying as much info as available, the code executes a DoCmd.Quit. If that's not enough to properly close the DB then I need to be enlightened. In my limited experience, such errors that cause the DB to Quit usually only happen during initial code development.
Thanks, I'll run the special explorer the next time I encounter the issue. It could be a NAS problem as mentioned by Micron. Good info here, I'll get to the bottom of the issue.