Access Database is getting corrupt again and again

Citrix itself does not resolve the issue, unless maybe your Citrix environment virtualizes apps using an older version of Windows. From what I understand, the issue is caused by the way the Access database engine in a Windows 10 environment communicates with the backend on the file server.

In the case described, and at another site I know of, Citrix is used to run the front end on a Windows Server o/s, so the front end is no longer running on Windows 10, which works around the issue and resolves the problem. Similar to using Terminal Server or a hosted Access service.

We have done some additional tests, and it appears the queries which we could use to produce the error are now working without the error.  Again these were queries that worked fine before this Microsoft updates from 2018 that began corrupting the database.

Having gone several months with no corruption issue, I am again wondering whether some Microsoft update has inadvertently corrected the issue.

Has anyone else, with current updates in place, tried to remove the work-arounds you may have in place to see if the issue has been resolved?

We are using Office 365.

That is a great option I have been thinking about, along with RDC'ing to a specific VM. Could also bypass our VPN altogether.

Thanks for the confirmation and encouragement, TQ.

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.