Feedback by UserVoice

Hans (Netherlands)

My feedback

  1. 40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Hans (Netherlands) commented  · 

    @uservoice moderator or dev team: How can I flag this item so that is also appears in the Datasheet category?
    Thanks,
    Hans

    Hans (Netherlands) supported this idea  · 
  2. 61 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Hans (Netherlands) commented  · 

    Same as "Fix Windows 10 1803 Frontend - Backend corruption issues" which has a lot more votes. Is there a moderator who can merge these two registrations of the same issue?

    Hans (Netherlands) supported this idea  · 
  3. 44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Hans (Netherlands) supported this idea  · 
  4. 173 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Access (Desktop Application)  ·  Flag idea as inappropriate…  ·  Admin →
    Hans (Netherlands) commented  · 

    @Access Team: Can you please give some insight into the underlying problem and the status of the resolution you are working on. It has now been over a year, and although we have been able to mitigate the problem somewhat, this is still a very very serious problem. If the problem persists my superiors (company directors) will choose to move away from MS Access and all other Microsoft products due to the unreliability and Microsofts inability to resolve problems within an acceptable timeframe.
    The main symptom of the problem is: Error 3343 Unrecognized database format.
    But I am guessing that the following two errors are probably also due to the same underlying problem:
    Error 3035 System resource exceeded.
    Error 3040 Disk I/O error during read.

    The recent Error 3340: Query <query name> is corrupt, gives my superiors more ammunition for ditching all Microsoft products. Fortunately, we were able to avoid a major disaster by disabling updates for Office, but (to my superiors) it seems Micosoft is losing control or just doesn’t care. Please help me prove my superiors wrong and fix these problems.

    Thanks,
    Hans

    Hans (Netherlands) supported this idea  · 
  5. 5 votes
    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 →
    Hans (Netherlands) supported this idea  · 
  6. 8 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 →
    Hans (Netherlands) supported this idea  · 

Feedback and Knowledge Base