Access Database is getting corrupt again and again

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?

I had this same problem running our database over a mapped drive or UNC path from our server (SBS2011) after introducing Windows 10 machines and a new Server 2016. Randomly the database would corrupt or crash when using it. I scoured the logs and found it coinciding with group policy refreshing in the back ground. To test the theory i opened the database and ran 'gpupdate /force' hey presto, corrupt and crashed database. It wouldn't corrupt all the time mostly crash. So I used group policy to 'turn off background refresh'........worked a charm.

1. Hold down the Windows Key and press “R” to bring up the Run command box.
2. Type “gpedit.msc“, then press “Enter“.
3. In the “Local Computer Policy“, go to “Computer Configuration” > “Administrative Templates” > “System” > “Group Policy“.
4. Open the “Turn off background refresh of Group Policy” setting.
5. Set this setting to “Enabled“, then select “OK“.

Hope this helps someone.

I don’t use Inno Setup, but I did evaluate it and still have it on my PC. The Inno Script Studio has a Registry section where you can add these values. That is essentially how I do it in the setup program I use.

Hi Mark!

Is it possible to clear these caches within VBA periodically, without needing to disable them altogether?

Thanks!

I don't know the answer to that.

Thanks Mark

Thats really helpful

I got this to work in ’Inno setup’ by creating a section in the setup file for [Registry] settings.

Much handier than running a batch file.

Is the consensus that these registry changes method is the unofficial fix?

Has anyone had a failure with this option especially with VB code rather than an Access frontend?

My VB6 program install file will include the new registry modifications and 

I will be testing this with users from this Monday onwards. I will post updates as I progress.