A family of Microsoft relational database management systems designed for ease of use.
Yes, this is an almost 2 year old bug.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Yes, this is an almost 2 year old bug.
I've been following this for a long time and from my understanding of the issue so far the problem occurs when there is a network connection between FE and BE.
Is it fair to say that this corruption issue does not occur where users are accessing the database via remote desktop where both BE and FE are on the same server drive?
Could someone please clarify that point for me?
Hi WayneAprato1!
That is correct! I have one client that provides the application on a server using remote desktop connections and they have not had this issue.
Hi George - this problem is limited to Windows10 clients accessing central data over a LAN. There were no reports of any problems on sites using mixed versions of Access front ends over the years. This Client side registry fix, applied to ALL win10 clients, will fix the problem, ie the constant corruption where the databases go into unrecognised state and worse. It is purely a LAN problem where Access on Win10 frontends accesses any .mdb or .accdb databases over a LAN. The problem has nothing to do with Access, it is just that Access databases are like canaries in the coal mine, the first to show problems, being extremely sensitive to any network disturbances. The issue introduced by Windows10 2 years ago has been constant. I think this is why the Access team can do nothing to effect a solution - it is the operating system that is causing the problem, and they have no control over it. There are too many other factors for the O/S dev team to consider, such as cloud compatibility and capabilities, for them to undo the changes that are causing this problem in Access over LANs. Microsoft want to make windows 10 the de facto o/s for accessing Cloud Services. The effect on Access is tiny collateral damage that they can't fix without causing other problems. Especially when there is a "FIX".
My advice: Implement the simple Client side Registry fix. It works. It will make your life easier.
Hope this helps you make a decision.
Hi Mgnagle,
I hear you and agree. Thank you for all the useful info, along with others who added more valuable updates.
I work for a huge organization which takes an act of the Congress & Senate to get anything done. Many layers of bureaucracy, divisions and departments. Trying to find the correct IT Support team which manages a particular server or updates a certain department's user laptops is like trying to find a needle in a haystack. Good news is that I am getting closer to getting someone to actually listening and responding to my numerous service requests.
I will be creating a summary of all the options posted here, along with yours and presenting it to the correct IT Support group, in addition to my CIO/Director. There will be a few meetings before anything is decided upon, let alone implemented. Unfortunately, the Coronavirus pandemic has thrown a wrench in the mix and made everything come to a crashing halt for now. So I have to keep fixing the frequent database corruptions as they come up.
This is the environment I have to deal with, but I am persistent and will get this issue finally solved. Thank you for your help and encouragement.
George