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.
I began outlining the list of every query and its type from these procedures and macros in their order to further study this conundrum. There are dozens, so hopefully over the next several days I can work thru this and test to see if any other patterns can be discerned.
Wow! Thanks for the detailed answer. I'm going to study this and check my app for any of those conditions. I did modify all the update queries after the query error fiasco but this is a different scenario.
Completed the list; which includes 31 delete queries, 65 append, and 53 update. These are just those executed during the "morning update" procedure in our database.
These affect both frontend and backend tables.
I would think that the queries affecting only frontend tables would not produce any issues regarding the Microsoft error. Just those affecting backend tables and of course when multiple users are logged in.
So, once I get back to a facility where I can test this, should be able to dig deeper.
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
Use the Feedback command within Access and provide all the details you can, including that the workaround isn't working. Be sure to include your email address. Maybe, someone from Microsoft will follow up.