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 server fix appears to be an official MS workaround. At least that is how it appears on their website.
Yes, fair enough. Perhaps it depends on the individual server setup whether performance is affected. 2 of my clients have employed the server fix without any performance hit that is obvious. I am regularly connected to both of these systems via remote desktop and they both perform well.
I suppose there has to be a reason why some servers suffer from the performance hit and others don't.
Like I said, what might work for you, might not work for someone else. These are developer suggestions.
Be warned - Performance can be affected dramatically by the server fix. That happened in my case until I had IT remove the fix after numerous complaints. The client side fix didn't work for me. Note that these are developer solutions, not MS solutions, which may or may not work. After 8 months, I had to go with the last resort which wasn't suggested here but by a couple fellow Access developers who went through the same database corruption issues. It's basically trial and error while the level of user complaints rise. I had to find a permanent solution.
Not sure what's going on there. Many users have found that the server reg fix stops the problem in its tracks as it did for me over 12 months ago. A client was experiencing daily corruption. After the IT contractor applied the server fix there have been no issues since.