Access Database is getting corrupt again and again

I agree it should be fixed by Microsoft. But in the interest of giving you and your clients some relief, I would urge you to try the client side registry change that has been suggested. It seems that is working for my clients without any downside so far. Also does not require a server change. Disable leasing on the server does work, so I suggest both to my clients, but the Windows 10 PC changes to the registry below seem to do the trick. Restart the PC after making the change and do it on every Windows 10 PC that uses the database. The only downside is that it only takes one Windows 10 PC without these changes to corrupt the database again. 

Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]"FileInfoCacheLifetime"=dword:00000000"FileNotFoundCacheLifetime"=dword:00000000"DirectoryCacheLifetime"=dword:00000000

We continue to gather information from customers, and are testing a new approach.

This is not a simple issue, and in addition to the difficulty of isolating the problem, we also have to be careful not to introduce new issues.

The initial fix we tested for this problem introduced new issues that were worse than the original problem.

We are working on this, and I will post updates when I have more concrete information.

Shane Groff

Access Engineering

For God's sake Microsoft!  Fix this.  It's been a year now and every damned day I have to deal with the same issue from a different location.  I have 30+ law enforcement academies that use an Access application and they rely on it.  The cost in lost productivity and the cost in lost credibility is not insignificant.  Agencies are reluctant to apply the "fix" which means that I get daily requests to get their systems back up and running. 

I am a contractor developer and do not have the permissions or scope to apply server fixes which means contacting their IT which means the old "We don't support Microsoft Access applications" routine and only adds to their suspicion of the product.

This alone may drive me into retirement.

So far the registry change on the Windows 10 client has fixed it for my user. She is no longer reporting the error. But it is regrettable that Microsoft hasn't addressed this problem. It's a big problem for companies that build Access solutions and companies that rely on Access to get work done.

I agree that it is regrettable that we are not given at least a response by Microsoft.  I have found so far that the change recommended to the Windows 10 client PCs as follows seems to have fixed the problem. I have been forced to implement this and move on while waiting for an official response. Disable leasing on the server has also worked.

Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]"FileInfoCacheLifetime"=dword:00000000"FileNotFoundCacheLifetime"=dword:00000000"DirectoryCacheLifetime"=dword:00000000****