E
erik.erikson
I mistyped and in cell $U55 wrote "=myfunction($U55)" (I meant to reference
$U54).
Unfortunately, I hit enter before noticing this and excel was hung for a
good while before I was able to pull up the VB console and halt the execution
of the formula (I was unable to do this in the main excel) window. However,
in halting execution, I was able to go back and edit the mistake. So, I'd
break execution and eventually was able to halt execution in the main window
at which point breaking in the VB editor caused a "self-reference" error to
come up (I assume in response to a stack overflow exception). At that point
everything was okay, and I was able to recover.
However, it took an entirely unnecessary 15-20 minutes to reach that end.
The check for self reference during script parsing is NOT that hard or
computationally expensive to do and I would have thought that by this rev,
this check would be standard.
Anyway, I regard this as a bug. Despite the lack of crash, the
unresponsiveness is a failure and I would expect most users to end the
process, thereby loosing data, see the application as unstable, etc.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...52fed0e&dg=microsoft.public.excel.crashesgpfs
$U54).
Unfortunately, I hit enter before noticing this and excel was hung for a
good while before I was able to pull up the VB console and halt the execution
of the formula (I was unable to do this in the main excel) window. However,
in halting execution, I was able to go back and edit the mistake. So, I'd
break execution and eventually was able to halt execution in the main window
at which point breaking in the VB editor caused a "self-reference" error to
come up (I assume in response to a stack overflow exception). At that point
everything was okay, and I was able to recover.
However, it took an entirely unnecessary 15-20 minutes to reach that end.
The check for self reference during script parsing is NOT that hard or
computationally expensive to do and I would have thought that by this rev,
this check would be standard.
Anyway, I regard this as a bug. Despite the lack of crash, the
unresponsiveness is a failure and I would expect most users to end the
process, thereby loosing data, see the application as unstable, etc.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...52fed0e&dg=microsoft.public.excel.crashesgpfs