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 agree totally - what we need in Microsoft is someone like Steve Ballmer who realises it is all about convincing Developers that Microsoft are a company worth investing our efforts in. Hopefully someone will take this seriously and fix it otherwise Windows 10 and its successor will be forever suspect.
Anxiously, waiting... : )
Thanks Gina. We haven't tried using the ACCDB to see if that helps.
Marty
Shane, I find it almost unbelievable that you aren't able to reproduce this. This issue has been causing many people major issues for many months and and all you have to report is that you can't reproduce the issue? Hard to believe to be honest.
I'll second that. I've had six agencies (clients) who have had this issue and a possible seventh cropped up on Monday. This reflects badly on us as developers as the users put the blame on us even though our applications have been running problem free for years up until this bug has appeared. It may not seem like a big deal to Microsoft but it's a big deal to those of us supporting applications who keep government and businesses up and running.
We've had to fight hard enough to be taken seriously when using Access to solve problems - don't make this more difficult. The majority of my clients are law enforcement academies with small budgets and the testing/training management systems I supply are affordable and effective.
Hi bignose2,
that is basically almost the same situation. The only difference is OS on the server (irrelevant from my perspective) and number of client computers (we have approx. 20 of them at our site, as of now 10x Win7 vs. 10x Win10).
Our client computers do extensive reads/writes to the database, so corruption surfaces fairly quickly (the more PCs run 1803, the quicker/more often we get corruption). As you have said, your PC with Win10 1803 is not used much - that could still be a culprit to not triggering database corruption.
Your point with single PC corrupting database while server having FE open makes sense, although it is new to me. It is still a problem in SMB Leasing implementation of the client computers where concurrency takes place. My example of 2 or more clients doing extensive work on the shared database backend would arguably cause corruption faster.
Otherwise your situation is very similiar: PCs with Win10 1709 -> everything is ok. After upgrading to 1803 -> corruption.
At one point, we will be testing Win 10 1809, but it is hard to do it right in the production environment while having other things to work on.