Forum Discussion

Wes_Jan's avatar
Wes_Jan
Copper Contributor
Jun 17, 2020

Unrecoverable Error

 

You all have probably made a typing, or other input, error.  In this case I made a typing mistake while entering the Data Type for a Test Table, as can be seen in the above screen capture.

 

And you all know to simply click on OK, the error box goes away, and you can correct the typing (or other) error.

 

I have used Access since at least 2003 and encountered now an error that I have never experienced before.  And that error is that there is nothing that I can do to make the error dialogue box close.  My only solution has been to end Access.exe via Task Manager.

 

This unrecoverable error also occurs in Access with other circumstances.  I have not noticed this problem in Word, Excel, or Outlook.  My version of Access is 16.0.12827.20336.

 

If anyone else is running this version of Access, could you create the same error as in my example and let me know whether you obtain the same result.  For the rest of you, any suggestions as to what to do?  I have tried not making any more errors, but this is sometimes difficult to achieve.

 

Thank you for your help.

 

This is my initial entry into this Community.

 

Wes Jan

33 Replies

  • Wes_Jan's avatar
    Wes_Jan
    Copper Contributor
    Bert: Would you know whether you have Text Cursor or Narrator active on your system? I am told that having either one of these active on one’s system causes the error that we have experienced. I did have Text Cursor active on my system and disabling the Text Cursor eliminated the Access error. I am told that MS now knows about this and will get a fix out in a few weeks. Wes
    • BertK1450's avatar
      BertK1450
      Copper Contributor

      Hi Wes, YES I had Text Cursor turned on (Narrator is off) and YES turning it off corrected the error loop problem. I tested the error first then turned Text Cursor off after which I could not duplicate the error. Great find! Good to hear MS recognized the problem and is correcting it.

      Thanks again Wes,

      Bert

      • George_Hepworth's avatar
        George_Hepworth
        Silver Contributor

        BertK1450 

         

        Wow. The last thing I would have guessed might well be a Windows Cursor setting that caused this. Thanks for persisting and thanks for posting your resolution. 

         

        One last thing. Do you mind posting a screenshot of where and how you change this setting? Future visitors might benefit as well from the visual.

  • Wes_Jan's avatar
    Wes_Jan
    Copper Contributor
    Bert: How intriguing. Unless I am not looking in the right place for this information, we don’t even share the same software. To find my Microsoft 365 – en -us version I looked in Control Panel/Programs and Features, and discovered install date of 7/16/20 and version 16.0.13001.20384. To find my Access version I opened an Access database, File/Account/About Access, and discovered Microsoft Access for Microsoft 365 MSO (16.0.13001.20338) 64-bit. I have 76 background processes and 101 Windows processes. Let me know what this all means? Thank you. Wes
    • BertK1450's avatar
      BertK1450
      Copper Contributor

      Wes,

      This is getting more interesting. Yes your locations for the versions are the same places I looked for mine except the Office version is also located in file/account/update options. I see you installed the 64-bit version which probably explains the version differences. I have the 64-bit Windows OS but I installed the 32-bit Office. I heeded the MS warnings about some external apps (and I think browsers) not compatible with the 64-bit version. But still with the differences in our systems and software versions we still have the same problem! Sorry I don't know what it means. I wonder if MS monitors these discussions.

      Bert

  • Wes_Jan's avatar
    Wes_Jan
    Copper Contributor
    Bert: I think it is fair to say that you know more about computers than I. I just thought that since you and I share the same Access problem and since no one else (including your wife) apparently does, that there must be something in common for us to have the same new error problem. If the key to pc’s is the motherboard and processor combination, would it be useful to focus on that and determine whether there is something in common. For example, I am told, that I have the unusual combination of two different graphics controllers running on my machine. My processor is the Intel i9-9980 HK. Do we need to check as to whether we have the same version of MS Office 365? I am happy that you were able to get the Esc key clear to work. Wes Jan
    • BertK1450's avatar
      BertK1450
      Copper Contributor

      Wes,

       We have a quite a different configuration, you have a much newer pc than I and I do not have any additional graphic controllers. I use the builtin Intel i5 graphics controller so that is not it. I have a basic hardware configuration, 1 SSD, 2 hard drives, blu ray and cd drirve, external speakers and a web camera. I installed my Office on 6/17/2020 and the version of Office is 16.0.13029.20308, Access version is in the attached file Access Version.pg (too long to type correctly).

       

      A quick check of Task Manager on my pc lists 71 background processes and 92 Windows processes, that's a lot of stuff running and who knows if one of these is the culprit.

      So we will keep looking/checking,

      Bert

       

       
       
       

       

       

  • Wes_Jan Hi Wes,

     

    Can you clarify what you mean when you say "there is nothing that I can do to make the error dialogue box close"?  Does clicking the button have a visual effect but not close the dialog?  Does the dialog close, but then immediately reopen?  Have you tried the 'x' in the upper right corner?  Does the 'Esc' key work?

     

    Could you attach a video showing the behavior?

     

    I can't reproduce the problem with the same build that you have.  When I click the OK button the dialog closes, and the list of valid types is displayed in the dropdown, which is what I assume you are expecting.

     

    Shane Groff

    Access Engineering

  • Wes_Jan's avatar
    Wes_Jan
    Copper Contributor
    George: I have been using Access for so long that the bulk of my databases are .mdb. But yes, the error occurs whether .mdb or .accdb. Wes
    • George Hepworth's avatar
      George Hepworth
      Iron Contributor

      Wes_Jan 

      I am going to have to send a note to a group of experts and see if anyone has any insights. The only other step I can suggest you could try would be to re-install Office 365.

      • Wes_Jan's avatar
        Wes_Jan
        Copper Contributor

        George Hepworth 

         

        Re-Install of Office 365 has already been done!

        I will await the insights from your group of experts.

         

        Wes

  • Wes_Jan Greetings.

     

    This is, indeed, a new problem that I've not seen or heard about.

     

    I am not sure about the version of Access from the build number, so can you clarify that?

    Office365? Office Pro 2016? 32 bit or 64bit? Thanks.

     

    I have a different build and can't replicate this problem, so knowing more about your version might help zero in on resources.

     

    Sometimes, a repair of Office can clear up problems like this. 

    • Wes_Jan's avatar
      Wes_Jan
      Copper Contributor

      George Hepworth 

       

      George

       

      As far as I know, I am using Microsoft 365 Personal, 64 bit. 

       

      And there are no pending updates for 365. 

       

      Thanks for helping me here. 

       

       

      Wes Jan

      • George Hepworth's avatar
        George Hepworth
        Iron Contributor

        Wes_Jan Thanks. The tech guys are into the build numbers more than some of us.

         

        I have a Pro Plus 64 bit version of Access, but I'm not hopeful that I'll see this problem.

         

        In the meantime, can you try to Repair the installation of O365 on your computer and see if that makes a difference?

Resources