This is the current Microsoft Access bug:
access-error-could-not-use-path-to-database-accdb-file-already-in-use-6cbc1560-62c2-46e7-9980-d079a46f5acc
how-to-revert-to-an-earlier-version-of-office-2bd5c457-a917-d57e-35a1-f709e3dda841
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
As of yesterday morning, one of the five computers in my client's office apparently began locking my Access mapped-drive back end files when we open the relevant local front end file on that computer. Once that computer has the file open, anyone else on another workstation (or I on the server), gets error 3045: "Could not use [path & back-end file name]; file already in use". The converse is also true; if I open the app on a different computer first, the problem computer gets the message when I try to run the app there.
Environment
Additional notes
What I have tried:
This all points strongly to a problem specific to the computer in question. It is as though there is some registry entry or configuration file on that computer indicating to Access Runtime that it should demand exclusive access to the backend, a setting that does not exist on any of the other computers. But I am not aware of any such setting. I can do very little diagnostics from the affected workstation, since it has only Access runtime. Also because it is runtime, there is no way I know of to explicitly request exclusive access when open a file (by opening the front end that has tables links to the BE).
Or it may be broader than Access, that is, it may be something requiring locks on all files. I am just lost after many hours of troubleshooting this after hours to try to avoid interfering with users' work--and soon it will be morning and they will be back at it again--without me having fixed it yet.
I halfway expected it to be something brought on by an update, but having done all the Windows & Office updates to multiple computers in my attempts to resolve the issue, with the problem still occurring on only one, I figured I had ruled out different Office or Windows update levels. I did look for recent updates on the faulty computer and one other, but there were so many updates installed there by the time I checked that I had no way of identifying any potential culprits, and I had not gone through computers comparing which ones had which updates.
But you have undoubtedly identified the issue, so I will assume that I just need to go through the faulty workstation and ferret out & remove the faulty update. Given that this is Access runtime, though, I am not sure the information on reverting to an earlier version will be relevant. This computer has Office Home & Business 2016 (no Access) and Access runtime 2013.
I will remove/reinstall Access runtime 2013--as I did yesterday, but not run any updates afterwards--as I did yesterday.
Thank you!