Unrecoverable Error

[Wes_Jan]

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

[#2]

@BertK1450 

Bert:

Just to be clear, your wife has an ASUS AMD, but your change was a new motherboard added to your original PC.  (What make is your PC?)

I don’t know the specs of your new motherboard.  Is there anything that we might share? (Looking for some common factor.)  Who writes the BIOS for you motherboard?

Can’t tell whether your Access problem would have existed before upgrading to MS Office 365.  I have had my Dell XPS for about 60 days, and I believe that my problem developed immediately, but I needed to install MS Office 365 to get Access.

FYI:  To escape from the error, I continuously hold down the Esc key and eventually the mis-typed entry clears, and I can type in a valid entry.

If you like, we can continue to see if the two of us working together can solve this problem.

Wes Jan

[#3]

Wes,

Yes, my wife's ASUS AMD PC is about 2yrs old. I built my PC 10 yrs ago and upgraded it 5 yrs ago. The key to the pc's is the motherboard and processor combination, everything else is off the shelf. I don't think comparing hardware will help, mine is older that yours, our hardware is different but we have the same problem. I did not have Access before upgrading to Office 365 and never had a problem with the other MS apps. Maybe we can continue to exchange any ideas/problems/clues we find during the use of Access. Maybe more users will discover this problem and respond.

Also, I can clear the error loop if I hold the Esc key down. Thanks for that tip. I was just repeatedly pressing the Esc key which did not work.

Bert

[#4]

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

[#5]

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

[#6]

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

[#7]

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

[#8]

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

[#9]

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

[#10]

@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.

[#11]

@George_Hepworth 

Go to Windows settings > Ease of Use > Text Cursor

Credit goes to Wes, he did all the investigation.

Bert

[#12]

@BertK1450 Thanks to both of you.

It boggles my mind that this setting would have such a debilitating impact on an Office application.

[#13]

@George_Hepworth 

George:

And I thank you for passing my initial message onto Shane, who has persevered on the MS end until a chance discovery was made, which allowed the identification of some possible causes.

Will await the MS "fix".

Wes Jan

[#14]

@BertK1450 

I think you have been kept in the loop to date.

But there is another issue that occurs with Text Cursor enabled on my machine.

Please see the attached word document

Wes Jan

[#15]

@Wes_Jan 

Thank you for the additional information.

Yes, this problem will be addressed as well with the same change.

Shane Groff

Access Engineering