Access Database is getting corrupt again and again

Agreed.  I have just given my clients having this issue a link the official MS super page on the matter.

https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state--7ec975da-f7a9-4414-a306-d3a7c422dc1d?ui=en-US&rs=en-US&ad=US

After that, I've never had any issue getting the registry fix applied.

Thanks for that link Daniel.

Has there been any more info from MS on a permanent fix and when that may be forthcoming? The cynic in me thinks they will just leave it at this.

I have one who refuses and I get a call every day, sometimes more than one call a day about the back-end data file crashing.

If it was me I'd be pointing them to this thread as evidence that the problem was created my MS and that now, 12 months later MS has failed to provide any viable fix other than the workaround, and that if the client refuses to use the workaround you will be charging them for your time when responding to calls relating to the issue.

You can lead a horse to water............

Wayne:  I've forwarded the link multiple times as well as every other suggestion and I've emphasized the importance of applying the recommended work-around to no avail and yes, I think that your point is a valid one; perhaps it's time to add a surcharge to my maintenance fees for instances when my recommendations are disregarded and result in excessive support calls.

This too shall pass....

Nope, not really. 

They posted that they had an update in early April stating that they were testing it, and nothing since.  No clue as to what is going on, MS doesn't communicate!  Your guess is as good as mine.

This very issue was the final straw with my largest client.  After being affected by various bugs and paying me, down time, and then this issue, he finally asked me to move everything away from MS.  I just finish the final release of their new web based system (a year in the making).  MS just doesn't seem to understand the damage that this issue is having on their reputation, but truthfully i don't think they care.  Access just isn't a priority IMHO.

Were you able to identify exactly what procedures/queries/macros, etc were initiated when the file became corrupt?

As indicated in previous response, we were able to identify back to back queries where there was a delete and then append query on the same table.  Adjusting these so they were not back to back and/or introducing a delay such as doevents, seems to have resolved the issue without having to use the workaround.  There may still be something else, but it has been 6-8 weeks now without the issue.