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.
The only workaround (not fix) is the registry hack and it applies to all versions, or at least Microsoft hasn't given any indication anywhere that it doesn't apply to all versions/OSes.
You run it on all PCs involved (front-end and back-end computers)
We are suddenly (starting last week) experiencing this issue as well.
The back-end database file is stored on server running Windows Server 2008 R2. Is there a workaround for this server version?
I installed a synology nas at our problem location to host the backend of our database. Works like a charm now for about a week. All computers running 1809.
No, nothing whatsoever.
Either revert/uninstall the update that causes the problem, apply the workaround or live with the continual corruption. Those are the options at this point in time.
Has anyone heard anything in regards to this issue? The panic and frustration in my office is increasing. The only new information I found is from the Access Dev Forum.