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.
So with each update, you have to reapply the registry fix after the update and hope it'll still work ?
Some of my clients had applied the registry fix and were stable for a while but it appears that the last Windows 10 update may have reversed that because suddenly I've been inundated with another rash of calls.
Good luck, Jaz ! I was in the same situation over 3 weeks ago. Calls/emails/texts every day, angry users at my desk, etc.
Boss had no suggestions, IT Support was unresponsive even though they caused this issue with the recent upgrade to Windows 10/Office 365. This fix saved my a**. Try it. If it doesn't work, go for the server fixes. But I think it'll work.
I created a subfolder below where my backend database used to exist then moved it there (on the same server). Once moved, I relinked the FE to the back end tables' new location and set the "Compact/Repair on Close" option. I cannot say if the folder move, relinking the back end tables and/or the Compact/Repair on Close is what fixed it, but it is fixed. Over 3 weeks later, no data corruption errors - Knock on wood. Sometimes the simpler solutions are the ones you try last.
I just tried this on a user's system. Fingers crossed and I'll report back if they stay stable for a week or so. I'm sick of getting these calls every day; I have a large number of clients so it really adds up in time down the drain not to mention the loss of goodwill. (Sorry about the whining.)
Correction: relinking the BE tables to the FE database...