Access Database is getting corrupt again and again

Thanks for the reply. Please if possible share the change

NAS devices are no magic pill, and not all created equal either.

I been called into companies where performance was dismal and the solution was to move it off of their NAS and suddenly everything was fine.

That said, I also do have clients running their database on a NAS  without issue.

The real solution here is to not use Windows 10 since it is it that is there for cause of this issue.

I also urge all of you to post on access.uservoice.com and through the feedback command with Access itself.  People need to make noise if they ever want this fixed.

Thank you! I too have been puzzled. What I suggested would disable leasing on one share limiting any performance or other impact dramatically and make it more palatable to customers and server administrators. I don’t have control of my clients servers so I can’t tell you for sure that it will work, but it should from what I understand. I made the client registry change part of our setup and that seems to be working. Some customers made the global disable leasing change on the server and reported that it worked. I suggested the change to just  one share to a few, but I do not have definitive evidence that they made the change and that it fixed the problem.

It seems like this would be a huge step forward if this approach works, at least as an interim step. The root cause still needs to be found and fixed by Microsoft. I hope they do not give up on this. I tried recreating it with a simple database doing repetitive queries, but was unable to. If anyone can do this and give it to Microsoft to help finally resolve this issue, they would be a hero and many of us would be very grateful. I do not like making the client change as I do not know the full performance impact of that change.

I can repost the share-specific change when I get to my office if that helps.

Two of my clients have used a NAS for back ends (long before the issue discussed here) and both were troublesome, so I would not personally go down that route except as last resort (but I assume it is a guaranteed solution to this issue). If necessary I would try Mark's method or stick the back end on a spare Windows PC and disable leasing on that. I have no idea how the performance on a fast dedicated PC would compare to that of a decent NAS though, in this context. Your issue seems to be with performance, so I suspect you will have to test the various options.

What If the backend access db is installed on a NAS Disk ?

Any experiences on that ?

I would prefer to buy to my customers a NAS Disk and install backends there, in order to get rid of this mess that MS gave to us and save my company from further problems ...

Any experiences regarding this ?