Feedback by UserVoice

Aleks R

My feedback

  1. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    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  · 
  2. 181 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →

    We are well aware of this issue and are working with the Windows team on resolving the problem. Although we believe we have a solution to the problem, it introduces some new issues that we need to investigate and resolve before we can deploy the fix.

    Thanks,
    Access Engineering

    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. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Aleks R shared this idea  · 

Feedback and Knowledge Base