MicrosoftGontranHarvey
Since your message is probably targeted at my comment: You are right, thanks for the reminder. We should not forget that the Access dev team (probably understaffed, like all IT teams nowadays) deserves a big "thank you" for providing us with such a great platform on which we can build our applications.
The reason for the current frustration is twofold. One issue is stability, the other is lack of communication.
In the last months/years, an unusual amount of bugs made it into the production release (mostly affecting the Current Channel, but in some cases also the Enterprise and/or LTSC channels). If you use Access as a runtime platform, your customers don't see Access crashing, they see your application crashing. And you can't point your customers to an official KB article describing the bug and the expected release date of a fix, because, more often than not, there is none.
I understand that the Access team is trying to make the best out of it, and if my comment came across as unkind, I sincerely apologize. From our outside perspective, we usually only see the product, not the PM having to personally take care of spam filtering. Thank you for your efforts, and I keep my fingers crossed that you get the manpower and resources you need to give this great product the love it deserves.
