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: Most helpful
Most helpful Newest Oldest
  1. 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
  2. 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
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  4. Anonymous
    2020-01-28T00:07:24+00:00

    I agree that this simple CLIENT SIDE registry fix works and has for the past 9 months. Apply this to every Windows 10 client. It works. forget about NAS and shares and applying any changes to the server.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]

    "FileInfoCacheLifetime"=dword:00000000

    "FileNotFoundCacheLifetime"=dword:00000000

    "DirectoryCacheLifetime"=dword:00000000

    This works and has for a long time. Every now and again this thread seems to forget this fix and all sorts of complicated solutions are proposed that do not work or have side-effects, requiring changes to central servers that compromise other applications.

    As RonNeer asked - is there anyone out there who has applied this reg change to EVERY window10 client,  and still had a problem?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-01-27T23:30:54+00:00

    Copy the following into a bat file and run on all client machines.

    It adds three undocumented lines to the registry. I have not heard of anybody that has tried this and it not working. If there is anyone who it has not worked for please post and let us know. It is documented earlier in this thread. I forget who first posted the solution but I am forever in their debt.

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]

    "FileInfoCacheLifetime"=dword:00000000

    "FileNotFoundCacheLifetime"=dword:00000000

    "DirectoryCacheLifetime"=dword:00000000

    Was this answer helpful?

    0 comments