Access Database is getting corrupt again and again

Mark - I was skeptical too but tried it & it worked. As I mentioned, I did three things (ie. Move the BE database to a different folder, relink the BE tables to the front end & switch on the "Compact and Repair on Close" option). I am not sure which action(s) fixed my daily database corruption issue, but it did.

It is a relatively simple fix vs trying to convince your IT Support to implement registry fixes on your host server or on all your client workstations. I would just try it, and if it doesn't work, go for the other server or client workstation registry fixes. Unfortunately, many developers gravitate to the more complex solutions rather than just testing a simple fix. I'd rather implement the simple fix and go on with my life. Just saying...

It does seem extremely unlikely that this will prove a permanent solution, but I guess moving the back end periodically could be viable for some sites where the Registry changes are not allowed. I wonder if simply changing the back end file name has the same effect (i.e. any change to the full (back end) database path).

This might partly explain the difficulty MS have in reproducing the issue; perhaps the (back end) database path needs to be in use for an extended period before the bug arises. (Also bearing in mind that various Windows Updates seem to have triggered it in many cases, and caching seems to be involved.)

Hopefully this will provide MS engineers with much needed clues. What do you think Shane?

George,

I guess I am amazed and a bit skeptical that just moving the back end database to a different folder on the server and relinking the tables on the front end would resolve anything. I am glad it is working for you and I hope it is not temporary. I am sure there are varying levels of how deep the path goes to the back end database as far as folders and sub-folders if we would survey the people here who are experiencing this problem. So I am wondering what the trick was in your case if this does indeed permanently resolve your problem. Or was there some other change that occurred at the same time such as the frequent compact and repair? I am just a bit puzzled by your results, while at the same time happy it helped you.

I'm new to this thread.

I'm relieved and not at the same time after reading these 33 pages.

I'm a small-time developer with 500 user sites,

Setup is : Access 97 on a shared drive on a Windows server

and PCs with  VB6 program installed accessing the database.

All going well for 25 years until past 6 weeks when all the clients had to get their PCs updated to Windows 10. 

I now have email phobia!

Just waiting for the next email to announce the dreaded  3343 database corrupt message.

Has anyone had persistent positive feedback on the simple option of  changing the folder of the database file on the server? 

from Daniel Pineault's site:

https://www.devhut.net/2018/06/13/access-bug-database-is-in-an-unrecognized-format/

MAKE A NEW FOLDER: As astonishing as this may sound, several users have now confirmed that simply creating a new folder (on the same drive) and moving their database to the new folder resolved the issue.

Has anyone developed a Bat file that removes the Disable_Leasing registry keys from the Server (runned with admin priveleges) ?

I wouldn't like to ask the ITs to remove manually these registry entries. I tried a lot to convince them run a single batch file with the disable leasing. Now asking them to remove manualy registry entries will be ... world war 3 !!!