Microsoft Access is not allowing me to compact and repair. Keeps saying its open etc

I have office 365 and tried reinstalling yesterday, but the problem still persists.

Here's another similar threads

https://answers.microsoft.com/en-us/msoffice/forum/all/microsoft-access-2019-could-not-use-filename-file/7876d6b0-4588-4059-8ad9-2c07ec5ce94a

I'm quickly repeat my suggestion:

My only suggestion at this point in time would be to revert your installation to a prior build that didn't exhibit this issue. It might take a little trial to get the right build though.

You could try the build that originally fixed the issue

https://www.devhut.net/access-lock-file-issues/ 

If that doesn't work, then start going even further back.

I'm sorry I don't understand. I didn't add out build anything to these databases. Might have been working in them, as normal, but I didn't make any changes to how it works.

I have used them for a number of years. So, I'm not sure what I would/could go back to.

It means to rollback Office Updates as one of them probably introduced this bug in your system.

If you review the following article, at the end, I have a series of links on this

https://www.devhut.net/access-lock-file-issues/ 

Or review

https://www.devhut.net/microsoft-office-uninstall-an-update/

Right, so whoever is following this thread and I hope that Microsoft certainly is, I think I have figured out with which systems this problem is occurring. I did a fresh install in another computer. This time I chose default office installation instead of 64 bit Office installation. And Voila - the same file works perfectly. Only thing is in all this hassle, my reports got corrupted and could not document those when using the documenter afterwards. So have deleted them. However with or without the reports the compact and repair worked perfectly. Someone had suggested, or I had read somewhere that one must compact the database while keeping the file closed so that's what I did. It was not different from what I was doing earlier in the other machine. So this is a big shoutout to Grover Park George who actually thought of this possibility and mentioned it in his reply. Thanks so much. For the time being till Microsoft fixes this for 64 bit systems, - all those having this problem just uninstall your office 365 and when doing a fresh install, use the default installation. DO NOT use the 64 bit installation. Since I did both in different machines I am confident that it is the 64 bit version that is causing the problem. Just install the default version and your problem will be sorted. Thanks to all who helped. And please keep this thread alive with your inputs and updates as this is a way to circumvent the problem. Microsoft still needs to come up with a fix. Thanks guys. Stay safe.

Ripal