Access Database is getting corrupt again and again

Good luck, Jaz ! I was in the same situation over 3 weeks ago. Calls/emails/texts every day, angry users at my desk, etc.

Boss had no suggestions, IT Support was unresponsive even though they caused this issue with the recent upgrade to Windows 10/Office 365. This fix saved my a**. Try it. If it doesn't work, go for the server fixes. But I think it'll work.

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. 

I just tried this on a user's system.  Fingers crossed and I'll report back if they stay stable for a week or so.  I'm sick of getting these calls every day; I have a large number of clients so it really adds up in time down the drain not to mention the loss of goodwill.  (Sorry about the whining.)

Correction: relinking the BE tables to the FE database...

I agree, David. Trying to get a fix installed on a host server or on all client machines require multiple levels of approval at my company. That is if IT Support is even willing or responding. This is not the case at my company, and frequently, you are left to find your own solutions. That is why I finally stumbled upon moving the BE database to another folder, relinking the BE tables to the FE data and setting the "Compact and Repair upon Close" option.

This is a quick, easy fix which worked for me, and I am in full control of. If you have to deal with multiple levels of company bureaucracy, try this first. If you are in a smaller company where IT Support is always available & willing, go for the server fixes mentioned previously.

To those who do not understand why the server side work around is still vital:

At many organisations the client configuration is also strictly controlled by IT departments. Only IT can "legally" apply any such Registry change, so it is up to them which solution(s) they try. In many cases, they will only try solutions recommended by Microsoft. Moving the back end to another folder, or even to a spare PC, in many cases will not require IT department approval, or such approval will be easy, so further test reports on this approach will be valuable. IT staff unwilling to disable leasing on a whole server, or to disable caching on multiple clients, may be willing to disable leasing on a single share used only for the back end, so test reports on this will also be valuable.

I hope that helps to clear up the confusion.