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

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.

The disable leasing fix works if applied on the server. You can alternatively apply the client registry change mentioned in this thread many times. Make the change below to each Windows 10 client PC that opens the database from a shared location. Then restart the client PC.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]

"FileInfoCacheLifetime"=dword:00000000

"FileNotFoundCacheLifetime"=dword:00000000

"DirectoryCacheLifetime"=dword:00000000

Both approaches have worked for me. The Windows 10 client change is usually easier to get approved for implementation on your clients network, so you might want to try that route.

If there are developers using the C++ MFC DAO classes and want to stop using Access database files, they can reply to the post.

I will make available some sourcecode with which they can open MySQL databases without changing their code!

So transfer your Access databases to MySQL or MariaDB, add my sourcecode to your Visual Studio 2017 Solution and off you go!

Never having to deal with MDB files and their problems again!

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

The DisableLeasing workaround mentioned many times in this thread works. The issue was driving me insane for a couple of months with one client until I asked their IT contractor to employ the workaround on their server. I've had no problems since.

Apparently the workaround also works if applied to all client machines rather than the server.

Any yes......it is totally unacceptable that after all this time MS is still floundering around and not providing a proper fix.