Access Database is getting corrupt again and again

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

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

George

FYI: A client who previously resolved this issue by applying the official MS registry patch has recently installed a new server, and moved the back end to this. As soon as multiple users started to use the database it crashed with this issue, error 3343. Since the official work-around worked before, it was obviously easiest to ask the IT staff to apply it to the new server. This immediately resolved the issue once again, with no performance hit and no mapped drive problems reported.

Thanks David. Good info - Keep it coming !!! Like the Coronavirus pandemic, we will also get through this Access database corruption issue, with or without MS's help.

George

Great post, mgnagle.  I too deal with only government and it is nigh impossible to find someone willing to make the changes.  I have written a document that outlines the problem and suggests three different possible solutions (with the Microsoft recommended work-around as #1) and send that to users to forward to their IST people.  Do they do it?  No.  Right now it's just all hands on deck for my agencies to get people up and running from home so for now I'll suck it up and repair databases.  I do think I'll add the RDP access solution to the document.  Thanks for the suggestion.