Access Database is getting corrupt again and again

Agreed.  You make several valid points.

I agree that migrating to SQL Server would be the best option. However, if the company does not want to commit to that conversion & as in my case, they are moving to a more proprietary, custom built system, their intent is keeping their Access database(s) running until a full migration to a new system can be completed.

I haven't heard that the performance with a SharePoint backend is awful. In fact, I heard the opposite from db analysts here who made the migration to SharePoint. In fact, I will be having a meeting with them later today to get all our questions answered.

Yes, moving on to another client/company is an option but given the recent pandemic, Federal administration transitions, and increasing unemployment, I'd rather stay put until resolutions regarding our national/international issues are more clear.

Just to be clear, my comment regarding migrating away from Access is based on years of bugs affecting both front-end and back-end and for which we have seen little come out of Redmond to actually fix them.  This current bug is a prime example.

When a company cannot support their product and resolve the issue they caused, yes i recommend going elsewhere. 

Migrating to another platform will obviously be more time consuming, but the payoff, for the clients I've done it for, as been phenomenal!!!  Not only are the solutions functional & stable, they are faster, work on any device (mobile, Apple, ...), I've been able to add new features that simply aren't possible in Access, ...  Add to that the fact that I've used open-source solutions, so no longer are my clients locked in and at the mercy of Microsoft's whims!  They can take their solution to any host, find any developer to help them, ...

Also, if you build using a proper framework, the build time can greatly be reduced.

Lastly, when I've migrated like this, we've used it as an opportunity to improve the solution based on everything we learnt building/using the original Access database.  This is the perfect time to address issues, tweak those flaws, add those "it would be nice" features to ...

So for me it's not just a question of speed of making the migration, but a big part of it was a request by my clients to get away from Microsoft as a whole because they felt burnt (they'd lost thousands of $$$ in downtime caused by this and other bugs) and completely abandoned and didn't want to be in that position ever again.

SQL express conversion is extremely expensive for complex DBs and provides a substantial performance reduction.

Class action lawsuit... Attorneys

Which is why I said "nearly all scenarios". Perhaps I should have added "in my experience".

The ease of conversion, and subsequent performance, in my experience, also greatly depends on how well the Access database application has been designed and built with respect to RDBMS standards.

SQL Server performance as a true RDBMS is far better than the Access DB engine for any large multi-user system (proven by numerous benchmarks). The problem is that a front end designed for an Access back end is likely to have certain specific performance issues when attached to a SQL back end. So, as Daniel points out, there is likely to be some degree of optimisation work required as part of most conversions. This is mitigated by the tools SQL Server provides to report exactly what is going on and pinpoint the cause of any performance issue. The solution is often a simple tweak to a query or index, for example, but sometimes it does require a significant rethink of the user interface design. This does make it very difficult to predict the time the conversion will take, which perhaps was the cause of NI's pain.

The context here is also important: my previous post was recommending SQL Server as a better solution than Sharepoint Lists in most situations. I understand that Sharepoint performance as a DBMS is generally awful. Compare also to Daniel's preferred solution; moving away from Access altogether. I would be very keen to hear about anyone who can completely replace a complex Access application faster and cheaper than I can convert it to SQL Server.

I wish it were that simple, Daniel. In large corporations, there are levels of management you have to present your suggestions to & they approve. If they don't approve, you don't move forward, and you have to come up with other options. Also a key question from mgmt is usually "What's the ROI on this idea ?". If they don't like your answer, again you don't move forward.

Saying you won't use their VPN to log in because Access doesn't work well with VPN's is not an acceptable position. You have to work within your company/corporate environment, whether large or small. And as you know, some environments are quite political, so it's not just about your preferred technical option.