Unexpected error; quitting

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jimatqsi
    Moderator Top Contributor
    • Oct 2006
    • 1290

    Unexpected error; quitting

    I am confronted with a brand new Access error / problem as of mid-afternoon US Eastern time on Dec 3. When editing a form in Access, I cannot click on an event's elipsis ... to get into the code behind the form. I get an immediate pop-up message that says "Unexpected error; quitting." The program does not actually quit, nor does it bring up the VBA code. I've tried multiple events of multiple objects in multiple forms and multiple database files, all with the same result.

    If one tries to launch the VBA editor (ALT+F11) nothing happens at all.

    I've tried multiple databases with the same result, on one particular machine (Windows 11 Pro). I've copied one of the databases to another machine and the problem does not occur there.

    If you search the internet for that error message text, you will find a Sep 2021 Microsoft article, very brief. It says only , "An unexpected error occurred, and Visual Basic was unable to continue. This may be a hardware problem or an effect of other software in your system." There's been no new software loaded recently, so I suppose it could be hardware related. There is nothing new on the workstation, so it would have to be a sudden failure of some component.

    This is extremely serious. I may start by replacing the machine, but if anyone has any suggestions or experience, I'd like to hear about it. I've tried the usual first step solutions, compact and repair, booting, closing all other programs etc ....

    Thanks for any advice you can offer.
  • NeoPa
    Recognized Expert Moderator MVP
    • Oct 2006
    • 32636

    #2
    Hi Jim.

    Sorry to disappoint you, but without any such experience my best guess as to what to do would be to try & find any recent updates to any of your software (Specifically Windows &/or M365/Office.) and try rolling it back. This assumes you find any within the relevant time window of course. Any updates applied and rebooted before the last point you know it was working correctly can be ignored. I suspect you've already looked at this as you've already tried the other option which would be a reboot.

    One last thing to try might be to find a version of the database from before you know it was last working & try that, but frankly the knowledge that you've already tried various other databases on that machine which all displayed the same symptoms makes that a rather forlorn hope.

    It seems there's little or nothing I can suggest that you haven't already covered so all I can really do is wish you good luck :-)

    Comment

    • isladogs
      Recognized Expert Moderator Contributor
      • Jul 2007
      • 479

      #3
      Which specific Access version / build / bitness / channel are you having problems with?

      Comment

      Working...