Access Database is getting corrupt again and again

Sorry but we have paid for MS Access, we have developed everything in MS Acces and we want to continue using this product, that used to be a revolution when it was commercialy deployed and now it is a deatroyed by the company that has created it. 

I am a pro developer in MS Access environment for about 15 years. And we all know that we were satisfied up to the version of 2003. This is why most of the devs are still using it. Was faster, more dev friendly environment and even more reliable. 

Now we experience bugs and corruption, because we did something wrong. And it is wrong to still stay with MS, that is not supporting our business and our customers. 

It has been 1.5 years with this bug. If you cannot reproduce the error, then for God's sake make a phone call or send an email to a couple of these people here in this thread that are having the problem. Get out of the cage and give solutions to people around that still believe in you. 

And please develop access again. I feel that you believe it is somehow an"internal competitor" to other products of ms. So my opinion is that you are doing this on purpose. 

My suggestion to all you around that you are hitted by this kind od MS practices. Instead of moving forward to another ms product for resolving the issue, I suggest to move away from MS. The time that you will need for migrating to another ms product, would be wiser to spend it to other sophisticated products that are out there. 

PS: Why there arent such bugs in SQL server? Because they pay more attention to that kimd of product and left access to suffer...

Thanks Shane. I am not experiencing problems at the moment and have not seen issues for many months.....touch wood.

One client that was experiencing continual corruption several months ago is no longer experiencing problems since the DisableLeasing fix was applied to the server. They are running Office 365.

Another newer client, also running Office 365, has not been experiencing any issues either. The DisableLeasing fix was applied to the server prior to the installation of their databases.

So, its been a few weeks with the work around in place on the individual workstations and it seems to be helping so far.  I had to do it on about a dozen systems and to be fair this database is older than dirt.  It needs to be rebuilt from the ground up.  Just glad I am not getting the daily complaints about the database being corrupted.

Can't you employ the workaround on individual workstations. That is reported to "fix" the problem.

I am actually trying that now... fingers crossed this will fix their issue.  I will report back if it did or did not.

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!