Access Database is getting corrupt again and again

I agree this client side change works and may very well have saved my business. The next important question is has anyone experienced any negative side effects to the database in question or any other applications or Windows itself after making this change? I do like this approach because I do not have control of the server configuration.

So the best advice to everyone. Make this change now to ALL Windows clients involved (and reboot) and your problems should cease. That is a until a new Windows 10 client without the change is introduced or the registry change gets overridden.

The server side change to one share I suggested has appeal if you have control of the server. Change just one place and it does not matter what the client side looks like.

Having said all that, Microsoft has to fix this. We should not have to go through this pain or have to apply these band aids. And who knows how long they will last. We have some fixes, but we need leadership from Microsoft to do ROOT CAUSE ANALYSIS and permanent CORRECTIVE ACTION. Basic problem solving technique.

Is Microsoft even listening anymore?

There was a noticeable performance issue on one  Windows 10 machine that I applied the fix to.

I had applied the fix proactively assuming that all Windows 10 computers were affected. Since this turned out not to be the case, i was able to revert the changes without experiencing the issue.

Ultimately i only needed to apply the fix to two machines to eliminate the problem.

That's fine as an opinion, but did you apply the DisableLeasing remedy and are still having problems?

https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state-%ef%bb%bf-7ec975da-f7a9-4414-a306-d3a7c422dc1d

Yes I have and it works fine. My issue is that it's a workaround at best, and who knows when it will break? MS is very good at breaking things as evidenced by the recent update query debacle. Testing seems to be a thing of the past. The users are the test bed.

It is beyond the bounds of credibility that they can't replicate this issue and then provide a proper fix after *2 years.*I'm not sure who they think they are kidding.

That's fine as an opinion, but did you apply the DisableLeasing remedy and are still having problems?

https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state-%ef%bb%bf-7ec975da-f7a9-4414-a306-d3a7c422dc1d

Microsoft has proven by its inaction that they don't give a flying flap about this issue. After 2 years that the issue has existed they expect us to believe that they can't even reproduce the problem....let alone fix it. That beggars belief and I just don't buy it.

I agree this client side change works and may very well have saved my business. The next important question is has anyone experienced any negative side effects to the database in question or any other applications or Windows itself after making this change? I do like this approach because I do not have control of the server configuration.

So the best advice to everyone. Make this change now to ALL Windows clients involved (and reboot) and your problems should cease. That is a until a new Windows 10 client without the change is introduced or the registry change gets overridden.

The server side change to one share I suggested has appeal if you have control of the server. Change just one place and it does not matter what the client side looks like.

Having said all that, Microsoft has to fix this. We should not have to go through this pain or have to apply these band aids. And who knows how long they will last. We have some fixes, but we need leadership from Microsoft to do ROOT CAUSE ANALYSIS and permanent CORRECTIVE ACTION. Basic problem solving technique.

Is Microsoft even listening anymore?