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.
Hi
Just an update on the NAS
We have not experienced a single corruption since i moved the backend DBs to the NAS
Still dont know why . . but it is working for us.
Cheers Paul G
Good day to you all.
I also directly feel the same pain. We built a finely tuned application that saved a metrology lab thousands of hours of tedious data entry, tracking, and admin organization.
Our original application was written in Windows 7, SP2 and Office 97. It evolved to it's best working state in Windows 7, SP3 and Office/Access 2003. In Feb. 2020, (not knowing about the corruption issue) it was translated to Windows 10, 1909 and Office/Access 2016, 1808, v.?, and of course that's when the front/back end data corruption issues started.
I'm looking for a solution, like everyone else.
I'm curious if anyone is cataloging attempts in any kind of scientific way.
There are literally hundreds of possible combinations and I'd love to see which ones have been tried.
Like, for example:
Windows 8 / Access 2007 / Server 2003
Windows 10 / Access 2012 / Server 2012
and obviously, there are different versions of every item, like the 10 versions of Windows 10 from 1507 to 2004. The hardware differences, too - like using servers as desktops and (I'm trying this one) Paul Gailiunas' idea of using a NAS (reply page #45).
For now, I believe we will revert to Windows 7, SP3 / Access 16 / Server 2016, unless I can figure out how to load Win 10, 1703 and stop all updates.
If you know of a catalog of attempts, please pass it on & I'll appreciate it and post my results there as well.
Good luck!
Yes, that is most exciting ! However, I tried one solution which was great for 3 months up until mid-March. The pandemic
forced most employees at my company to start working remotely and accessing the network via VPN (ie. not constant
connection to the DB).
Your solution may be fine for small companies which give you full control of their databases, network & servers. However,
with large corporations/government agencies with thousands of employees & several IT Depts, it is almost an impossible
task to do the changes you propose.
While I applaud your energy, enthusiasm and interest in finding a solution, I have become skeptical of "one size fits all"
solutions which will definitely fix your IT issues. Time and time again, the solution you need is frequently found through
trial and error.
Yes !!!
I have done this up to now to two customers. The oldest situation works almost a month without any corruption !!! So I guess that the constact connection to the Db or the cache changes might do something. This is why I would like someone else to check it out
So I read your lengthy post. You opt for the Server fix at first then add several coding, registry and database object changes to improve the performance. Then you remove the Server fix, and it magically continues to work flawlessly & quickly for the past 4 weeks ? Have I summarized your fix correctly ?