Access Database is getting corrupt again and again

What sort of reception are people getting from the IT department when they ask them to disable leasing on the server and client machines in medium to large organisations? I have a small client of about 15 seats that has a contract IT provider and have had to ask him to incorporate the workaround. This wasn't an issue and network performance seems to still be ok.

I have a feeling that it would be an issue with a larger organisation who has their own IT department. Just this morning I've been asked to provide a quote to just such an organisation. I don't know for sure yet, but I think they are using Windows 10. I'm now in a position where I could supply them with a highly unreliable system with the only way of fixing it being to ask IT to incorporate a workaround that they may not be willing to do because of the reported side issues such as impacted network performance. 8 months? into this issue it should no longer be an issue.

Well said Wayne.

I suggested a few months back that Microsoft could easily contact someone on this list who has current sites experiencing the problem and, with permission from their customer, give them remote access so that Microsoft engineers could examine log files etc.  Surely they would be able to determine the cause - it is a matter of assigning enough resources to finding a solution.

My fear is that as more of our customers are forced to move over to Windows 10 as computers are replaced etc,  that our currently stable sites will start to experience regular data corruptions due to this problem. Not a prospect I want to face and explain to customers.

Hi Shane. Ok, I take back the "bozo" term but a LOT of people are extremely frustrated by this issue. It is having a very negative impact on both developers and their clients and has been present for a very long time.

I don't understand how you can say that the problem is not reproducible. This issue has many people tearing their hair out. I question the amount of resources that are being deployed to find a fix.

Hi Wayne,

There is a third possibility, which is that Microsoft is testing a solution and will provide more information when they have definitive information to share.

Access is almost thirty years old, and a lot of the core code hasn't changed much for a long time.  As the operating system develops and changes, sometimes it exposes things in the program that used to work, but now may encounter issues.

It can indeed be difficult to isolate an issue that is not reproducible so we can't examine it directly, and sometimes that means it takes time to understand it. We also want to make certain that when fixing this problem, we don't introduce any new problems.

We are interested in fixing the problem, and I will let you know when I can give you more concrete information.

Shane Groff

Senior Bozo Engineer

The question in my mind is "will this ever be fixed?". That workaround was posted 7 months ago and still the bozos at Microsoft seem to either have no clue on how to fix the problem or they aren't interested. These are the only 2 possibilities that come to mind that could account for the fact that it hasn't been addressed. It absolutely beggars belief. :(