Bunchil
asked on
system error &H8000FFF (-2147418113
Hi All, I have just updated an xls file created in 2012 with a few changes and have saved it as an .xlm with Excel 2013. Now when I try to run the file I get the system error message that subsequently causes Excel to crash.
Can any one tell me how to fix this please.
Bunchil
Can any one tell me how to fix this please.
Bunchil
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi byundit, thank you for your response. The VBA error I found was minor and stupid and so do not wish to take any credit for solving my problem. I had made some changes to the VBA code with a result that one section of code called for a subroutine that no longer existed in any of the VBA modules. This caused the system error that occurred when I tried to run the code after saving, closing and reopening the file.
Nonetheless, that is the answer to your question. Certainly not anything that I posted.
Normally, you get a different error message when one of the subs is missing. In the VBA Editor, does your Tools...Options...General dialog look like mine? If not, that may be why you are seeing a different error message.
Normally, you get a different error message when one of the subs is missing. In the VBA Editor, does your Tools...Options...General dialog look like mine? If not, that may be why you are seeing a different error message.
ASKER
Thank you byundit, my general dialog tab in the VBA editor appears exactly the same as the one you showed so I don't know why the error message I got.
Does the missing routine have the same name as a sub in a library that you have reference in your project (Tools...Options...Referen ces)?
I apologize for belaboring the point, but you should have gotten a runtime error and the debugger would have pointed you to the exact statement calling the sub that didn't exist. The fact that you didn't, makes this problem much more interesting.
I apologize for belaboring the point, but you should have gotten a runtime error and the debugger would have pointed you to the exact statement calling the sub that didn't exist. The fact that you didn't, makes this problem much more interesting.
ASKER
Hi byundt no it doesn't. The routine referenced undertook a regression analysis and the code for the analysis was in the routine referenced. I was cleaning up and simplifying (??) my code and renamed the routine that undertook the analysis and called the new routine directly from a command button.
Originally, the command button called a routine (now obsolete) which then called the routine (now renamed) that undertook the regression analysis
Originally, the command button called a routine (now obsolete) which then called the routine (now renamed) that undertook the regression analysis
When I Googled for your error message (Excel error 2147418113), there were a number of disparate hits with fixes noted. Have you performed such a search and checked the leads out? Since you didn't post the file or describe what it contained, it is difficult to suggest anything specific.