Access Database is getting corrupt again and again

In another state the application is used at several locations where they each have their own server, but they connect via a front end on the desktop and the backend on the server.

When the issue began, after extensive testing, we identified a series of queries that would produce the error.  Since this was a once a day procedure, it is now initiated at the beginning of the day with just one user logged in, and logs others out before beginning.

This took care of 99 percent of our issues.  (We decided against the workarounds provided by Microsoft or the community.)

Still once in a while, say 3 to 6 weeks we would still get the error.  We have a simple utility that each location uses to compact the database and then they are back up and running.

BUT, it has been several months since we have seen the error at any of our locations.  I wonder whether there has been an update which has been installed that inadvertently resolved the issue?  I will go back and test to see if we can still duplicate the error as before.  If not, maybe we are out of the woods?

I agree that Access still has a lot going for it.

We have an application in one state where everything is on one server.  Users access the app thru Remote Desktop Connections, so that there session is created on the server with a fresh frontend, and it accesses the backend which is on the same server.  Hence there is no data transferring across the network, just "Screen shots" thru the Remote Connection.  This scenario bypasses the issue which is related to multiple users sharing data across a network.

After dealing with this Access data corruption issues for the past two years, nothing is obvious. Microsoft has basically given up on the problem and left customers hanging.

I haven't given up on Access yet. Though the backend database has its issues with Windows 10/VPN's, the front end tools, VBA coding and interactions with other Office/Adobe applications is quite versatile.

I agree with BP. Though not the best option, moving the Access backend database to SharePoint also takes the Access database engine/Windows 10 backend communication out of the equation. SharePoint may not require logging into the company VPN, which I suspect also causes data corruption issues with the Access backend database.

I have multiple clients using Citrix and it has resolved the issue for each of them. Obviously it will depend on the server OS being used, but for my clients it has completely bypassed the issue they were having with their individual desktop OS.

Have you tried it and still experienced problems?

Then again, heading on 3 years now, I think the wise move is now to move away from Access, but that's just my personal/professional opinion.