J
JBonyun
I have a re-creatable crash when the user clicks the
formula bar (e.g. to type in anything) after running
Solver, in Excel 2003.
It doesn't happen for just any Solver problem, as far as
I can tell. I have a workbook with the following basic
characteristics, that it always happens to:
- about 1500 rows
- uses SUMPRODUCT, LN, NORMSDIST once on every row
- uses STDEV, SUM once in the workbook
Solver is set-up to maximize the SUM by changing 4 input
cells (which affect each of the 1500 rows).
Solver runs successfully. But after clicking "Ok" to
dismiss Solver, if the user immediately clicks on the
Formula Bar, there is an instant crash. Various
combinations of "immediately" and not-so-immeidately
might also cause the problem.
Now for the weirdest bit: it apparently makes a
difference what the contents of the active cell are. If
the active cell contains a constant/string or is blank,
it will crash. If it contains a formula -- any formula --
it won't (or at least not as consistently).
I'm sure this isn't going to trip-up the majority of
users, but it really messes with my application. Anyone
have ideas?
(And, as an aside, why the heck doesn't MS have a bug
reporting form somewhere? Do you guys really not care at
all?)
formula bar (e.g. to type in anything) after running
Solver, in Excel 2003.
It doesn't happen for just any Solver problem, as far as
I can tell. I have a workbook with the following basic
characteristics, that it always happens to:
- about 1500 rows
- uses SUMPRODUCT, LN, NORMSDIST once on every row
- uses STDEV, SUM once in the workbook
Solver is set-up to maximize the SUM by changing 4 input
cells (which affect each of the 1500 rows).
Solver runs successfully. But after clicking "Ok" to
dismiss Solver, if the user immediately clicks on the
Formula Bar, there is an instant crash. Various
combinations of "immediately" and not-so-immeidately
might also cause the problem.
Now for the weirdest bit: it apparently makes a
difference what the contents of the active cell are. If
the active cell contains a constant/string or is blank,
it will crash. If it contains a formula -- any formula --
it won't (or at least not as consistently).
I'm sure this isn't going to trip-up the majority of
users, but it really messes with my application. Anyone
have ideas?
(And, as an aside, why the heck doesn't MS have a bug
reporting form somewhere? Do you guys really not care at
all?)