Access Database is getting corrupt again and again

I have a situation where 4 networked PCs have just been upgraded to new hardware. They were previously running Windows 7 and there were no issues.

One of the PCs, the "Admin" machine hosts the data file and the database frontend on that Admin machine and the database frontends on the other 3 PCs points to the data file on the Admin machine.

Corruption has started to occur with the new hardware running Windows 10. What is the best approach? Should the client reg fix be applied to all machines?

I haven't explicitly been faulted, but have had several clients decide they were done with Access over this, and other bugs that cost them thousands in downtime, and simply go to other development companies (didn't even get the chance to quote on the project and these were long term excellent clients of mine - that alone tells me who they are blaming at this point).

So they don't directly blame me, but they have taken their business elsewhere.

And just because they don't say things directly to me, that doesn't mean this doesn't hurt my image/reputation as i was the one who recommended Access, and since they've decided to go elsewhere, do you really think they're going to recommend my services to others.  So at the end of the day, this bug (and others) have cost me clients, and the potential for future work and/or referrals.

I truly don't think Microsoft understands the black eye that these continual bugs have given the product and as a consequence developers.

Enough said.

Daniel, you are correct.  The implication in the earlier rant (not mine) was that our applications are "simple desktop" applications which doesn't begin to describe the things we as developers are creating.  In my case I know that my main application that is in use in 40+ different agencies has a limited life span and I've been asked to consult with a government agency to replace it.  I will make money consulting but by essentially putting myself out of business on that particular front.  In my case I'm working toward retirement so it's not a big an issue as with other developers.  

But there is always going to be a need for accessible and affordable solutions and I maintain that Access is still a great tool for that.  I also have several other complex applications that will most likely outlive me. I would prefer to keep an amicable relationship with the people like Shane who are trying to help rather than pound my desk making demands. 

We would do well to focus on answers from management - any ideas on that?

Our reputations do not need to suffer if you approach this problem with your users in a calm and helpful manner.  So far no one has faulted me nor abandoned their applications.

What I've learnt over the years, the Dev Team members are truly great people that try to do everything within their power to to improve the product.  

That said, there is a limited number of them & they are spread very thin.

In this particular instance, they are having to deal with an issue caused by another group of developer as this isn't an issue of their own making which makes things much, much more complicated.  From my understanding (and i could be completely wrong - only someone from Microsoft can confirm our not) is that the reason Microsoft can't/won't simply undo this patch is that it is security related.  So security of the OS trumps the stability of our databases.

I too have lost some serious business to this bug and am very upset with this, and several recent bugs that are putting my livelihood at risk.  My only answer at this point is to migrate my client's away from Microsoft.  I think truthfully this is all any of us can do.  There only so long businesses can wait and personally that time had come and gone for me and my clients.

My beef is with MS' management.  It is their failing to take this issue seriously and allocate sufficient resources to fix this issue within a reasonable time that is the true issue. Obviously, more people need to be involved in remedying this bug, but this isn't Shane's fault.  He should be commended for trying to keep the channels of communication open with us and being bluntly honest in his responses.  A few years ago, when i was starting off as an MVP there was no communication with the Dev Team whatsoever, so this alone is a huge step forward!

So thank you Shane for everything you do and please don't take any of our frustrations, rants,... personally!

Good point, Jaz. There is only so much one employee can do in a big company.