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.
Daniel, do you think the 1809 release this week will contain a fix for this issue? There's one machine that is crashing a database every couple of days. This never happened until some time after the 1803 update.
![](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(256, 41%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETV%3C/text%3E%3C/svg%3E)
I did move the BE to SQL Server, took about 3 days, but this is a COMPLEX application that was never designed for it, and performance in some critical areas was terrible. We rolled back. I am not completely giving up on it, but a lot more work would have to be done before this can fly.
My hope is that MSFT networking team finds the problem and fixes it.
NOTE to some posters here: this is not an Access problem; it's a networking problem that Access suffers more from than others.
You are absolutely right. Moving the back-end to SQL Server is no small task and introduces major support issues for those of us who are not in-house. As you pointed out, many of us have mature but extremely productive projects that have been stable for many years. We do not deserve to be ignored.
When a company ignores its MVPs (and there are several pitching in on this one) then we know we are in serious trouble and the implications that has for the substantial investments we have made in that company's products. We now know we were mistaken to invest in Access all those years ago but all was ok up to about 1 year ago. People who suggest moving the backend over to another product have no idea the amount of work that entails for a mature product that has been deployed for over 10 years with no stability issues until recently.
The solution here is that Microsoft start taking this seriously and locate the fault. I am sure there are many developers out there who are having the same problems.
Thanks Daniel.