Aleks R
My feedback
-
246 votes
An error occurred while saving the comment Aleks R
supported this idea
·
An error occurred while saving the comment Aleks R
commented
I know I'm just venting, because Microsoft is "well aware of the issue", but holy cow, this is ridiculous. 15+ months and the problem is still happening? We have lost clients over the last year because of Microsoft's update fiascos. And the craziest part is that those fiascos keep happening. New update = new problem and new calls from clients who blame us. Even when we can get them to understand that it's Microsoft, not us, it doesn't matter, because that doesn't solve the problem. I'm so very tired of this crap.
-
3 votesAleks R
shared this idea
·
-
2 votesAleks R
shared this idea
·
-
135 votesAleks R
supported this idea
·
-
2 votesAleks R
shared this idea
·
-
2 votesAleks R
supported this idea
·
-
2 votes
Microsoft Access Product Team
responded
Thank you for reporting this issue – the Access team is investigating this and will inform you about next steps. For now, please proceed with the workaround that you have included in your description.
An error occurred while saving the comment Aleks R
commented
NB: Access updated to 16.0.12730.20342 and still have same problem.
Aleks R
shared this idea
·
-
1 voteAleks R
shared this idea
·
I believe this is the same issue as is discussed in this link: https://support.microsoft.com/en-us/topic/access-reports-that-databases-are-in-an-inconsistent-state-7ec975da-f7a9-4414-a306-d3a7c422dc1d?ui=en-us&rs=en-us&ad=us
(There have been SO many Access issues that I've gotten them confused in my head.)
Their last update July 9, 2020, states that the fix they had planned led to other problems, so they are "continuing to work on the problem".