Access Database is getting corrupt again and again

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....

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.

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.

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............

So there is no fix other than moving from Access?  I just charged a client for this database and now how to tell them it won't work because of MS bugs and a serious issue that has been outstanding with MS for over a year???  What is the alternative?

SO FRUSTRATING!  Agreed.  Totally unacceptable

Don't despair. The disable leasing WILL work. If you can get your client to apply it.  I have several who have done it and all is quiet.  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.

I am testing a beta version of my app where I create delays between consecutive delete/append processes and should know soon if that helps with the recalcitrant agency that won't apply the leasing fix.  The easy, no, facile answer you will often get is "move to SQLServer" but that's not always the appropriate nor necessary solution.  If your app runs well under Access and doesn't have mega data files then you are just fine sticking with Access which still has many very important benefits in a relational DB environment.