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, its been a few weeks with the work around in place on the individual workstations and it seems to be helping so far. I had to do it on about a dozen systems and to be fair this database is older than dirt. It needs to be rebuilt from the ground up. Just glad I am not getting the daily complaints about the database being corrupted.
Can't you employ the workaround on individual workstations. That is reported to "fix" the problem.
I am actually trying that now... fingers crossed this will fix their issue. I will report back if it did or did not.
Our users have started reporting similar issues with the latest round of updates to Office 2016 / Win 10 1803. They repair the corrupted database just to have it do it again for seemingly no reason. We can't apply the "workaround" because that is our main file server and would impact other stuff. I will try the client workaround but its really poor development if you have to apply workarounds and they haven't addressed the issue in an year! Seems like every "creature" update we get, they screw us over in some fashion and break something. Hard to support systems when they constantly give you a moving target. Small businesses can't afford to pay the extortion fee for Enterprise.
Can't you employ the workaround on individual workstations. That is reported to "fix" the problem.
Shane Groff......are there any updates on this issue? You indicated some time ago that a permanent fix was in the pipeline.
Our users have started reporting similar issues with the latest round of updates to Office 2016 / Win 10 1803. They repair the corrupted database just to have it do it again for seemingly no reason. We can't apply the "workaround" because that is our main file server and would impact other stuff. I will try the client workaround but its really poor development if you have to apply workarounds and they haven't addressed the issue in an year! Seems like every "creature" update we get, they screw us over in some fashion and break something. Hard to support systems when they constantly give you a moving target. Small businesses can't afford to pay the extortion fee for Enterprise.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more