Access Database is getting corrupt again and again

PSS: I did the "Make a New Folder" solution & it worked for me for a few weeks. I tried the server fix & performance was awful. Client fix didn't work. Again, a solution that may work for some situations, doesn't work for all situations. Many variables could be involved.

P.S. I recently tested the "Make a New Folder" solution (create a new folder on the same drive and move the back-end database to the new folder) and this did NOT resolve the issue for this client.

To David, personally I rely on the recommendations of my colleagues who rolled back their backend Access databases to Access 2013 (32-bit) late last year and have had no issues since then. All other posted solutions I've tried either only work for a few weeks or not at all.

I agree with you on IT Dept not allowing non sanctioned MS fixes. It took a lot of convincing to have them try the server fix, which ended up impacting performance almost immediately. You take a credibility hit after that, and they're not so welcoming on your next suggestion.

I fault Microsoft with not taking this issue seriously, coming up with a fix that works across the board & treating Access like a defunct database waiting to be pitched (a al FoxPro, DBase, etc).

That July 9 post could be referring to a proper fix that they have been working on which has undesirable side effects.

That is certainly how I read it. It is some small comfort to see that they are still working on it. But if anyone at Microsoft is reading this, PLEASE rewrite that whole status box on the official bug report page; it is now very confusing and contains now redundant statements. Many thanks for taking the time to update us periodically; for any future updates, please include the year in all dates to reduce confusion! Finally, the Microsoft recommended workaround is not practical for some users due to the performance hit on some networks, so please also include a warning and an alternative; for example, the "client file cache registry hack" detailed many times in this thread and also at https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/ has apparently worked, with no side effects, for everyone who has tried it. But in my experience some IT departments will not allow any Registry edit which is not sanctioned by Microsoft, so this solution is not available to all Access users.

To txaa30, Personally I doubt that rolling back the version of Access will work permanently in all cases, since we know that the bug can affect all recent versions. What was your IT department's response when you showed them the official workaround?

It is a fix that Microsoft was working on internally.  It was never released publically because their internal testing revealed issues.

The only thing we have gotten in over 2 years is the server registry workaround and that was actually suggested in a public forum by a user and later adopted by Microsoft as their official workaround.

Thanks Daniel. So MS didn't even produce the workaround. Now I'm really full of confidence. :)