Access Database is getting corrupt again and again

Thanks Martin. Wise advice. I will let you know how things go.

George

Hi George  I understand your situation as I also deal with a few government organisations and know the difficulties getting them to make any changes, especially registry changes. The stridency of my position is to try to reassure those in your position, that it is worth going down this track as it will produce the desired solution. Some of the comments in the thread would have you believe it may/probably will/will not/ will work/ will cause slow downs etc etc   - this is no state of mind to be in if you have to go through the wringer to get something implemented, thinking it MAY or may not work after all that effort. My experience is it works and can be deployed easily as a .reg file that the IT departments can run themselves.  Go for it. I know how I felt before this solution was posted - I was looking at a very grim situation for my business, worsening every day as more and more of my customers were forced to move to Windows 10. It has been plain sailing for the past 9-10 months with no corruptions. A great relief. 

An even better solution is the Terminal Services (RDP) access to the server, where all the clients run on separate profiles on the data server - this removes any LAN access, which fixes the problem,  is much more robust, and a million times faster for any Access application. Deploying is then just a matter of configuring the RDP client on almost any type of computer, a 2 minute job. not always possible to arrange, but if everything can be kept on the same server, i.e. rdp user profiles and backend data, it is magic.

Hope this helps. Martin

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

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 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.