Access Database is getting corrupt again and again

Good point, Jaz. There is only so much one employee can do in a big company.

Sir, I am polite to Shane because while Microsoft may be a big company Shane is a human being doing a difficult job.

I have rolled back 10 users to Access 2013 32-bit version. No issues, no data corruption so far.

Note - I have found connecting via VPN to the backend database can cause performance and possible data corruption issues. However, our LAN is not available during this pandemic, so we have to make due. Fortunately, our VPN IT team has been responsive to issues.

I have also added a couple email warnings to myself when the database opens & a user cannot connect to the backend database (VPN is not connected) or the backend database is corrupted. Gives me a quicker heads up to any potential db issues, so I can address them immediately.

Thank you Shane.  Perhaps occasionally you could provide any insights you have as to what anyone there knows about it.  We are pretty much in the dark and any light you can shed is greatly appreciated.

Sorry my friend JAZSchaefer but you are very polite to Shane Groff. We do not expect any highlights or any insights from him/her (I do not know) or from anyone in MS. They are joking with us. We want a stable resolution to this. And this has to be done NOW.

Microsoft is able to put a devil in a bottle. All these software, RDBMS, .NET, Servers, SQL,, Windows etc. They know exactly what they have done and simply they do not want to resolve it or take back the changes they made with that damn update of Windows 10 that cost us our companies and our lives.

WHY ?

Simple:

Access is able to do the job for the biggest majority of companies with simple desktop apps and with simple networking. And also has a good deployment. It is just ... a file. And they do not like this. This is why they are killing access slowly after 2010. Because access was a simple revolutionary idea that would be always alive and confront with all these SQL Server and .NET apps for desktops ... All these, in most cases for small companies, are like having an expensive Nuclear Aircraft Carrier to go for fishing. Also why to invest on Cloud Dbs since Access is ... cheap and does the job. And since they are not having the guts to make a clean statement: "Access if over for us", they made this on purpose to just take out the biggest advantage. Access ability to work in network environments. So they will keep it alive for a single desktop but dead for companies that require network access of their dbs.

And you my friend that you are reading this and you believe that I am over reacting, just think about it.

MICROSOFT is a GIANT and cannot resolve an issue that they have created by their own with an update of windows, after two years.

And if you are still having second thoughts, then read it again:

MICROSOFT is a GIANT and cannot resolve an issue that they have created by their own with an update of windows, after two years.

If there will be no resolution to this, then I believe that we need to think the legislative way to push Microsoft and gain back the money we have lost and our reputation. In EU there are specific rules about issues like this.  I will go forward and inform a Greek Member of the EU Parliament with a link of this thread, since this issue had a huge impact to the viability of our companies as also our customers. I just cannot accept Microsoft doing this. Sorry ...

PS:

Please someone try another potential workaround that I have posted just a few post before. It might be a good alternative as it also gives better speed.

That is so sad and unnecessary, Stratos. I know what you're going through. I dreaded logging on in the morning, only to be informed by users that the database was corrupted again. After a while, you get tagged as incompetent and wonder if you'll get called in for a "Sorry, we have to let you go" meeting.

Unfortunately, you have little choice as a developer on what software products a company decides to use.