Access Database is getting corrupt again and again

Anonymous
2018-06-01T17:47:41+00:00

We have an application which was working okay till last month. But after the last windows update our clients are getting issues with access database. access database got corrupted.  We ran compact and repair. But it still getting corrupted again and again.  This issue started right after the window update. clients are on different OS. Like server 2018, server 2012 and windows 10.

Is there anything i have check in new windows update or any other step to prevent database corruption?

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

604 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Tom van Stiphout 40,216 Reputation points MVP Volunteer Moderator
    2020-01-28T03:14:14+00:00

    That's fine as an opinion, but did you apply the DisableLeasing remedy and are still having problems?

    https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state-%ef%bb%bf-7ec975da-f7a9-4414-a306-d3a7c422dc1d

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-01-28T02:11:57+00:00

    Microsoft has proven by its inaction that they don't give a flying flap about this issue. After 2 years that the issue has existed they expect us to believe that they can't even reproduce the problem....let alone fix it. That beggars belief and I just don't buy it.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-01-28T01:58:16+00:00

    I agree this client side change works and may very well have saved my business. The next important question is has anyone experienced any negative side effects to the database in question or any other applications or Windows itself after making this change? I do like this approach because I do not have control of the server configuration.

    So the best advice to everyone. Make this change now to ALL Windows clients involved (and reboot) and your problems should cease. That is a until a new Windows 10 client without the change is introduced or the registry change gets overridden.

    The server side change to one share I suggested has appeal if you have control of the server. Change just one place and it does not matter what the client side looks like.

    Having said all that, Microsoft has to fix this. We should not have to go through this pain or have to apply these band aids. And who knows how long they will last. We have some fixes, but we need leadership from Microsoft to do ROOT CAUSE ANALYSIS and permanent CORRECTIVE ACTION. Basic problem solving technique.

    Is Microsoft even listening anymore?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-01-28T01:47:19+00:00
    1. Do these changes require administrator rights?
    2. Can these changes be made thru VBA?
    3. Can these changes be made just for the current msaccess session?

    Thanks!!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-01-28T00:35:38+00:00

    As RonNeer said, I have been running this fix for over a year now and no problems anymore.  I didn't even have to apply it to all my users.  Just the ones that were having the issue.  I didn't have to do anything on the server.  But I realize everyone's environment is different.  Now I am just faced with having a database that nobody here remembers when it was created (it is that old) and needing to bring it up to modern times.  I feel like that would resolve this issue where the fix would not be needed.  Best I can tell our database was created in Access 2000.  LOL.

    Was this answer helpful?

    0 comments