Access Database is getting corrupt again and again

I created a subfolder below where my backend database used to exist then moved it there (on the same server). Once moved, I relinked the FE to the back end tables' new location and set the "Compact/Repair on Close" option. I cannot say if the folder move, relinking the back end tables and/or the Compact/Repair on Close is what fixed it, but it is fixed. Over 3 weeks later, no data corruption errors - Knock on wood. Sometimes the simpler solutions are the ones you try last.

Any ideas on what made the difference? Was the database moved to a different server or just a different share on the same server?

My prior post probably got lost or overlooked.

I moved my Access backend database to a different network folder then relinked the backend tables to the FE db. I have the Compact/Repair on Close option set. We have about 25 - 50 people accessing this database daily. Since I did this change over 3 weeks ago, there have been no more data corruption issues.

I tried to get IT Support to install the Disable Leasing fix on the Host server, but they haven't been responsive. So I came up with this above last ditch option when our database was corrupting multiple times daily, and I had to do something !

I would at least give this option a try if your IT Support group is as unresponsive as mine or the Disable Leasing fix isn't working. It was a lifesaver for me.

George 

Note - Users have their own compiled FE database which is copied to their local drive (C:) when a new db version is released. I don't have users create shortcuts to the network compiled/uncompiled FE db.

My prior post probably got lost or overlooked.

I moved my Access backend database to a different network folder then relinked the backend tables to the FE db. I have the Compact/Repair on Close option set. We have about 25 - 50 people accessing this database daily. Since I did this change over 3 weeks ago, there have been no more data corruption issues.

I tried to get IT Support to install the Disable Leasing fix on the Host server, but they haven't been responsive. So I came up with this above last ditch option when our database was corrupting multiple times daily, and I had to do something !

I would at least give this option a try if your IT Support group is as unresponsive as mine or the Disable Leasing fix isn't working. It was a lifesaver for me.

George

Here is what I posted two months in a reply to Shane Groff from Microsoft on this forum on this topic. I did not get a reply. I also posted this once or twice previously to everyone and got no replies from anyone who might have tried it. Pretty simple and worth a try.

1. Create a folder on the server and place the uncorrupted database in that folder.
2. Share the folder on the server and give it a share name (e.g., MyDB)
3. Start Powershell as Admin on the server.
4. Set the leasing mode for the new share to None with the following commands:

    set-smbshare MyDB -LeasingMode None

    get-smbshare MyDB | Format-List -Property *    (make sure Leasing Mode is set to None)

5. Restart the server or do NET STOP SERVER then NET START SERVER.
6. Make sure ALL the client PCs open the database file or point to it in a front-end database using the UNC path for the new share name. If they don't use the right share name, disable leasing will still be on.

Note: To turn leasing back on if needed (in case of problems):

    set-smbshare MyDB -LeasingMode Full     (then restart the server or do NET STOP SERVER then NET START SERVER)

To repeat, THIS NEEDS TO BE FIXED BY MICROSOFT. None of the workarounds, including this one and the client based one, are acceptable as a permanent condition of using Microsoft Access on a network. Just unacceptable. IT IS GOING ON TWO YEARS!!! This is a flaw in the Microsoft Networking SMB protocol that needs to be resolved.