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 there is no fix other than moving from Access? I just charged a client for this database and now how to tell them it won't work because of MS bugs and a serious issue that has been outstanding with MS for over a year??? What is the alternative?
SO FRUSTRATING! Agreed. Totally unacceptable
Tried all the fixes, got all the updates, front end on latest windows 10 build and backend on server 2016.
nothing works, the database is now getting corrupt so often that it is unusable and we are having to look to moving to alternative non microsoft software. need an immediate update to fix this problem but since Microsoft have known about this for around a year and done nothing about it then i'm guessing they wont, this is unacceptable.
Look forward to hearing about your results.
TQuasar: Thanks for responding. I am trying two different methods; one is converting the back-to-back delete/append queries to one make table query (setting warnings off). The other is adding in a 5 second wait between the delete and append queries. My volunteer beta tester won’t be doing any of the processes that use these queries for about 10 days from now so I won’t know if it succeeds until then.
However… If they don’t have any database “corruption” in the interim that would indicate that it may very well be the queries as they do not come into play in any other part of the application. Again, thank you for submitting your clues.
Hi JAZShaefer!
Sorry for the delay in responding.
Most instances just required a reordering of the delete queries, so they were not immediately prior to the append query to the same table.
There was one instance where I used DoEvents between the queries, which seemed to alleviate the problem.
Hope that helps!