About an hour ago, Excel started crashing when ever a VBA compiler error
was encountered. I did a little testing and the following happens
every time
1. there is a problem in a macro, could be as simple as a misspelled
variable (Option Explicit is "on")
2. when the macro compiles, it stops at the problem and displays the
normal ambiguous error mesaage
3. I look at the error and fix it (or not, does not matter)
4. I exit the VBE and get the message that this will stop the
debugger
5. I click OK and Excel crashes about 5 seconds later with the
wonderful "Microsoft Excel for Windows has encountered a problem and
needs to close"

Once I have this crash, many other things cause a similar crash, e.g.,
just closing a spreadsheet. If I reboot, I can do normal things, but
if I have a VBA compiler error, the process starts again.

Does anyone have any idea what is going on here?

Thanks


---
Message posted from http://www.ExcelForum.com/

MWE,

Sounds like one of the VBA DLL files got corrupted. I'd uninstall
then reinstall.


--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com


"MWE " wrote in message
...
About an hour ago, Excel started crashing when ever a VBA
compiler error
was encountered. I did a little testing and the following
happens
every time
1. there is a problem in a macro, could be as simple as a
misspelled
variable (Option Explicit is "on")
2. when the macro compiles, it stops at the problem and
displays the
normal ambiguous error mesaage
3. I look at the error and fix it (or not, does not matter)
4. I exit the VBE and get the message that this will stop the
debugger
5. I click OK and Excel crashes about 5 seconds later with the
wonderful "Microsoft Excel for Windows has encountered a
problem and
needs to close"

Once I have this crash, many other things cause a similar
crash, e.g.,
just closing a spreadsheet. If I reboot, I can do normal
things, but
if I have a VBA compiler error, the process starts again.

Does anyone have any idea what is going on here?

Thanks


---
Message posted from http://www.ExcelForum.com/

With Excel closed,
Try deleting files in your temp directory and subdirectories under temp that
appear to be related to Excel or VBA.
Then reboot.
--
Regards,
Tom Ogilvy

MWE wrote in message
...
About an hour ago, Excel started crashing when ever a VBA compiler error
was encountered. I did a little testing and the following happens
every time
1. there is a problem in a macro, could be as simple as a misspelled
variable (Option Explicit is "on")
2. when the macro compiles, it stops at the problem and displays the
normal ambiguous error mesaage
3. I look at the error and fix it (or not, does not matter)
4. I exit the VBE and get the message that this will stop the
debugger
5. I click OK and Excel crashes about 5 seconds later with the
wonderful "Microsoft Excel for Windows has encountered a problem and
needs to close"

Once I have this crash, many other things cause a similar crash, e.g.,
just closing a spreadsheet. If I reboot, I can do normal things, but
if I have a VBA compiler error, the process starts again.

Does anyone have any idea what is going on here?

Thanks


---
Message posted from http://www.ExcelForum.com/

Chip/Tom: thanks for your replies. I tried Tom's (simpliest) but tha
did not help. Before I tried uninstalling and reinstalling Excel,
spent some time backtracking to the original problem and also wen
"sideways" to see how many Excel applications would misbehave (use
copies). Every Excel appl I opened had the same problems; many faile
as soon as I hit the enable macro button. Reinstalling Excel fixed th
problem with all appls except the one that started it all. It wa
still messed up and I ended up deleting it and going back to an earlie
version (luckily I had done a backup of that drive yesterday).
believe that the root cause was an attempt to dupliicate Publi
declaration from a base application in an Add-in specificall
constructed to hold a subroutine library used by the base applicatio
and several sister applications (you both replied to my thread abou
global common). When I started testing the base application after
did that, Excel puked and I spent the next 5 hours trying to figure ou
what went wrong. Any idea why that action would create such havoc?

Thank

--
Message posted from http://www.ExcelForum.com