Access Database is getting corrupt again and again

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

The problem still persists. I have sunk hours in to this and I need to make decisions for my clients based on whether there will be 

a solution for this problem in the foreseeable future. 

Have you been able to receive more concrete information on the issue?

Any information on what is causing this problem would be helpful.

I would make the registry change on each Windows 10 client that uses the Access files that are on the SMB share (then restart the PCs). I don't know anything about Synology, but if you make the above change on the Windows 10 clients, it will probably resolve the problem. If Synology has the equivalent of Disable Leasing, you could try that too or instead.

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

I have a client with a small environment where the Access Files are stored on a Synology hosted SMB share. We are only seeing this issue created by 2 of the 5 Windows 10 Clients which are on build 1809. Can I expect this workaround to help even though only applied to those 2 client machines or do I have to modify parameters on the Synology too? I am Thankful for any advice.