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,
What exactly does the client registry fix do, and why does it resolve this Access database corruption issue ? Before I recruit a tech with admin rights and we proceed to update 40-ish client laptops, I want to have some assurance this fix will work.
Let me know - Thank,
George
I must have misunderstood your posts. I thought you said you had been running on an .accdb front end db and a back end .mdb successfully for the past couple months, without data corruptions.
Hi Everyone - ie fellow crash victims . .
On our system we have a main backend DB that was stored in a seperate RAID harddrive box. - It floated between 200meg and 300meg in size and was stable with 20 users.
After we installed a new server box HP Proliniant ML350, we moved the backend tables to a Raid array inside the server box. It did run faster, but we also started experiencing the corruption issues.
most commonly around 8.30 - 9.00 am as staff started logging on. sometimes it would crash several times in 1 day.
we tried fixing networks points - cables - switches etc - thinking it was some sort of packet crash causing the corruption. . . nothing worked.
about 6 weeks ago i moved the BE tables back onto the external RAID box - and have not had a crash since . .
The big question is WHY . . mysteries of the universe . .
Cheers
PaulG
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
Bad news - The switch to .mdb hasn't stopped the data corruption issues. My database has corrupted twice since I implemented the change.
I am now considering Plan B - The client side registry fix. However, I am curious what exactly this registry fix does if someone could explain.
Thanks,
George