Share via

Can't Compact and Repair Database in Access 2016

Anonymous
2020-03-05T09:28:36+00:00

Hi guys,

I've been having lots of problems trying to compact and repair databases. I keep getting the message "Could not use [file path/DB name]; file already in use.

The file is not being used and there are no temporary files in the folder. I have also rebooted.

So, I tried to create a new database. I imported 4 csv files and manually compacted after each import. Everything worked ok. I then closed the database, reopened it and, as a test, tried to compact again. I got the same error even though it had run ok before I closed and no changes had been made since.

The database is 133mb which I think is well within the size limits.

Can anyone offer a suggestion how to fix this? It is infuriating!

Thanks

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-03-20T18:44:38+00:00

    Hi guys,

    Thanks for all your replies.

    It turns out that Google Drive was causing the problems. The folder containing the database backs up to Google and the syncing process meant Access thought the file was in use. By waiting until syncing has finished the compact works fine.

    Thanks again for your help.

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-03-05T15:42:40+00:00

    The above post is a scam.  Do not call that number or contact them in any way!  I have already reported the post.

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2020-03-05T13:46:38+00:00

    Scott is right, would the following link apply to your situation?

    https://www.devhut.net/2020/03/02/access-bug-ldb-laccdb-not-going-away/

    0 comments
  5. ScottGem 68,810 Reputation points Volunteer Moderator
    2020-03-05T12:17:54+00:00

    Hi James, I'm an independent adviser and will try to help.

    I've seen several reports of this message. I believe the problem stems from a recent update which affected the lock files. Try taking that new database you just created and copying it to a different folder, then see if it will C & R. If it does, make sure the lock file is gone after you close the file and then reopen and try the C&R.

    You can try rolling back the updates until the next one. Hopefully this issue will be fixed soon.

    0 comments