Access Database is getting corrupt again and again

Make sure the the 'reconnect' option box is unticked if you use the GPO drive map option. That will definitely fix it, did for me.

Hello Tomas. 

Thanks dor the reply. 

What do you mean by saying reconnect option box with GPO. Where can we find this.

I am also condirming the following:

1. If we are using the server disable leasing option, everything seems fixed. If this option is selected then corruption returns (but not so often) through mapped networked drive and corruption is not appearing again when using unc path for linking to the back end. 
2. The other solution, the SMB registry fix, that is applied only on client machines, has a tremendous impact on speed, especially when using dlookups or dsums. The server disable leasing solution is also having a speed impact but is by far faster than SMB registry fix. 
3. Tried the erd solution that mentioned here. The "turn off background refresh of group policy". So I dissabled all other solutions, made a clean restart to serveer and client machines, apllied this to server, rebooting again everything and checked. Didnt worked for me, so I am asking Thomas to help with the "unticked" reconnected option box with GPO which I do not understand, so I will try again

Sorry, drive maps using GPO is as link:

https://community.spiceworks.com/how_to/79280-mapping-network-drives-folders-via-group-policy

Thanks a lot

Unfortumately with this solution I connected through UNC path and finally had a corruption. I didn't test it through a mapped network drive. Is there any chance that something else might happened? Any ideas?

I am also condirming the following:

1. If we are using the server disable leasing option, everything seems fixed. If this option is selected then corruption returns (but not so often) through mapped networked drive and corruption is not appearing again when using unc path for linking to the back end. 
2. The other solution, the SMB registry fix, that is applied only on client machines, has a tremendous impact on speed, especially when using dlookups or dsums. The server disable leasing solution is also having a speed impact but is by far faster than SMB registry fix. 
3. Tried the erd solution that mentioned here. The "turn off background refresh of group policy". So I dissabled all other solutions, made a clean restart to serveer and client machines, apllied this to server, rebooting again everything and checked. Didnt work for me

Hello Theodorus,

Many thanks for confirming your test results, particularly my suspicion that the SMB registry fix on clients can impact performance. Your experience with using the server disable leasing option with mapped drives is also invaluable. Great work.

What about the hack as mentioned before (and on Daniel Pineault's site) of changing the Client's File cache as below. Does anyone report an impact performance with this? This is the option I have chosen in the past 2 weeks.

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

What about the hack as mentioned before (and on Daniel Pineault's site) of changing the Client's File cache as below. Does anyone report an impact performance with this? This is the option I have chosen in the past 2 weeks.

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

This is the SMB registry fix that was mentioned above. It works well but with a huge performance impact