This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
We have an application which was working okay till last month. But after the last windows update our clients are getting issues with access database. access database got corrupted. We ran compact and repair. But it still getting corrupted again and again. This issue started right after the window update. clients are on different OS. Like server 2018, server 2012 and windows 10.
Is there anything i have check in new windows update or any other step to prevent database corruption?
A family of Microsoft relational database management systems designed for ease of use.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
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.
Any solution that takes Windows 10 out of the equation will resolve this issue.
By using Citrix, the user is actually operating directly on the Citrix server, so Windows 10 is taken out of the equation, problem solved.
It is Windows 10 that is causing this issue, so using another OS gets around the problem.
Windows 7 never looked so good! :-)
Another solution is Citrix: I do not recall it being discussed in this thread, See Access - Bug - Database is in an Unrecognized Format | DEVelopers HUT (devhut.net) thread starting 1st Feb 2021.
But I guess this is much the same as running the front end on Terminal Server, which I think has been discussed here.
Thanks for the advice, Dave. After significant research, I decided SharePoint isn't the option I'm looking for. Perhaps SQL Express or SQL Azure may be.
I found this article - Thoughts ?
https://sharepointmaven.com/how-to-overcome-sharepoint-5000-item-limit-threshold/
I think you would be far better off spending the time converting to SQL Server Express or SQL Azure, rather than fighting with a tool designed for a completely different job (document management). And if your database just happens to be primarily for document management, then perhaps abandon Access and design a proper Sharepoint system.