Access Database is getting corrupt again and again

I don't think the DisableLeasing fix is being referred to in that post as not working.

The way I read it is that other fixes that have been trialed since have not delivered the desired outcome.

Thanks Shane. I am not experiencing problems at the moment and have not seen issues for many months.....touch wood.

One client that was experiencing continual corruption several months ago is no longer experiencing problems since the DisableLeasing fix was applied to the server. They are running Office 365.

Another newer client, also running Office 365, has not been experiencing any issues either. The DisableLeasing fix was applied to the server prior to the installation of their databases.

Hi Wayne,

The biggest problem with this issue is that we still don't have a way to reproduce the problem in a controlled environment.

Nobody has been able to give us a situation where it is "Do these steps", then "Database is corrupted".

We believe we understand the change in Windows that caused the increase in corrupted databases, and have been testing changes that we hope will alleviate the problem in production.  Initially, that will be for O365 Monthly Channel users.  It will not necessarily address all the issues, particularly in environments with users using different versions (if someone using Access 2016 corrupts the database, it may still be reported as corrupt when it is opened in Access365).

I am not suggesting this as a workaround, because I know it isn't a trivial transformation, but if this is causing you significant issues, it is worth considering using Access for the front end, and storing data in  SQL Server.

We will share more information when we have it, but I don't want to make promises we can't deliver on.