Access Database is getting corrupt again and again

For anyone that it monitoring this thead for updates on the issue, this started to happening to my DB very recently (two users only, Win 10 PCs, back-end on a Linux NAS). No real problems before.

I tried the registry hack that involves the FileCache - it seemed to work to stop the corruption, but made the DB so slow it wasn't worth persevering with, I ended up reverting back, and just C&R the back-end when the corruptions happens.

Sadly therefore not a viable workaround for me!

And as I have a NAS for the back end, not Windows/Windows server, I can't try the DisableLeasing hack. I have today tried this on one front-end machine though, see how that goes....

Thanks Daniel. Much appreciated.

The file leasing is done on the server, the file cache is done on each client pc. They are 2 different and distinct workarounds.

https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/

"In one of the a friend with better operating system understanding applied the 3 registry changes to FileInfoCacheLifetime, FileNotFoundCacheLifetime and DirectoryCacheLifetime."

Are these normally applied on the server or on each client? Can you please link me to them?

Thank you to everyone posting on this blog, especially Daniel Pineault.   The discussion, over 2 years old now, has been of considerable help in understanding the options.

I look after a number of Access databases for small businesses, local government, and even a couple small Access applications for our city's police.     Most of the have the data tables in a separate Access database and the forms in another.   Often it has been better that each user have his/her own copy of the front end database.  A number of them are hitting the "frequent compact and repair required" problem.  Only the back end database needs compact and repair when the problem occurs, except for a couple simpler ones which have the tables in the same database as the forms.

In one of them, for a swimming pool maintenance company, a friend with good operating system knowledge applied the 3 registry changes to FileInfoCacheLifetime, FileNotFoundCacheLifetime and DirectoryCacheLifetime.    Before that fix the 5 users had experienced multiple needs for compact and repair, often within minutes, and many times in a day.   That was a good 3 months ago.  Since then they have had no problems requiring compact and repair.   So far it has not been possible to try that fix for a number of other Access databases that I've built and look after because I'm an independent developer and the government and police IT support staff are reluctant to change registry settings.  They are afraid the often numerous other applications also used by the sometimes 20 or so affected Access users, may be adversely affected.   I don't know enough to assure them the 3 registry changes won't cause problems to some other application.

Another relevant piece of information is that another Access database I've built and looked after for a couple decades has used SQL Server for its data tables and Access for the forms.   This database, or rather its Access front end with the forms, has never had the "need for frequent compact and repair" problem.  Presumably the back end data tables aren't vulnerable to the problem, as they are not held within Access.   I note that the conversion of the back end from an Access database to SQL server, using ODBC, has been, for the several I've handled, a lot of work -- scores of hours, if not hundreds of hours -- so it's not an easy fix.

In checking the information from Microsoft about later Windows 10 versions, such as Version 1903 and Version 1909, there doesn't seem to be, as far as I can see, any indication of a fix the "compact and repair required frequently" problem.