MsAccess error 3046: "could not save; currently locked by another user"
Let's recap. This is my current understanding:The app is deployed with the FE on each workstation, and an Access BE on the server. Server permissions have been checked and are OK. Sometimes without...
View ArticleMsAccess error 3046: "could not save; currently locked by another user"
We updated the permissions but we still have had 2 users get the error.
View ArticleMsAccess error 3046: "could not save; currently locked by another user"
I have the same problem with vendor software using Access DB started happening also Dec 6th. Our vendor says it is a microsoft problems.They told us to roll back to earlier version of windows 10...
View ArticleMsAccess error 3046: "could not save; currently locked by another user"
One way this can happen is if either the Share itself, or the folder of the share, don't have the right permissions. Assuming you are on a Domain network, make sure all users have update rights.Don't...
View ArticleMsAccess error 3046: "could not save; currently locked by another user"
I have the same new problem:"could not save; currently locked by..." in a multiple user environment
View ArticleMsAccess error 3046: "could not save; currently locked by another user"
Sorry for the late reply: Christmas holidays...The users have their own copy of the frontend and the backend is also an Access database.The weird thing is that has run for years this way and all of a...
View ArticleMsAccess error 3046: "could not save; currently locked by another user"
Does each user have their own copy of the front end of their own hard drive? Or are they sharing a network copy of the FE?Is the BE an Access database or something else like SQL Server?
View ArticleMsAccess error 3046: "could not save; currently locked by another user"
The last couple of weeks (since the 6th of december, 2019) we get this error. We work with a MsAccess application in a multiple user environment (split database). The program (frontend) did not not...
View Article