I've written a VBA routine, making some calculations, and every time
I've run through it, a #VALUE error appears. Now when I press Ctrl-Alt-
F9, this error goes away, and all the numbers that I wanted to obtain
appear, which is fine, but is there any way of preventing the error
appearing in the first place, or is this just a bug in the underlying
program (which is Excel 2003)?

In addition to this, I currently have 2 workbooks open, and when I
press Ctrl-Alt-F9 to clear the errors from the first one, all the
results obtained in the SECOND one are changed into #VALUE errors.
Similarly, when I press Ctrl-Alt-F9 to clear the new errors from the
second one, all my nice data in the first one reverts back to #VALUE
errors. There are no links between the workbooks; they contain
standalone calculations. Methinks Excel has a bug.

On 7 Aug, 16:30, wrote:
I've written a VBA routine, making some calculations, and every time
I've run through it, a #VALUE error appears. Now when I press Ctrl-Alt-
F9, this error goes away, and all the numbers that I wanted to obtain
appear, which is fine, but is there any way of preventing the error
appearing in the first place, or is this just a bug in the underlying
program (which is Excel 2003)?

Before I blamed excel, I'd guess that my code was misbehaving.


wrote:

In addition to this, I currently have 2 workbooks open, and when I
press Ctrl-Alt-F9 to clear the errors from the first one, all the
results obtained in the SECOND one are changed into #VALUE errors.
Similarly, when I press Ctrl-Alt-F9 to clear the new errors from the
second one, all my nice data in the first one reverts back to #VALUE
errors. There are no links between the workbooks; they contain
standalone calculations. Methinks Excel has a bug.

On 7 Aug, 16:30, wrote:
I've written a VBA routine, making some calculations, and every time
I've run through it, a #VALUE error appears. Now when I press Ctrl-Alt-
F9, this error goes away, and all the numbers that I wanted to obtain
appear, which is fine, but is there any way of preventing the error
appearing in the first place, or is this just a bug in the underlying
program (which is Excel 2003)?

--

Dave Peterson