Share via

Access database in inconsistent state

Anonymous
2020-07-29T22:49:06+00:00

This is an FYI for those who have had this problem. Today we started to again experience this error with our backend database on a network share.  According to this post, a fix for this has been in the works for quite some time.

https://support.microsoft.com/en-us/office/access-reports-that-databases-are-in-an-inconsistent-state-%EF%BB%BF-7ec975da-f7a9-4414-a306-d3a7c422dc1d 

The workaround is to add a registry entry to disable leasing which we had done many moons ago.  Last night the PC with the backend database was upgraded to Windows 10 2004 and as a result the registry entry for disable leasing was no longer there. When I added it again, the problem was resolved.

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

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Tom van Stiphout 40,091 Reputation points MVP Volunteer Moderator
    2020-07-30T04:02:26+00:00

    If I read the article correctly, if you have deployed the app per best practices, with BE on the server and FE on each workstation, you would have only needed to disable leasing on the server, regardless of how many workstations use the app.

    0 comments
  2. Anonymous
    2020-07-30T09:34:57+00:00

    Yes, I've seen this happen as well.  The update seems to reset many settings with no regards to what was previously setup.

    @Tom, yes, that is correct.  The Microsoft workaround only applies to the BE server/PC.

    0 comments