Nick Hodge wrote:
> Bill
>
> It really depends on your code. If it runs for that length of time you
> should make sure it releases all variables on each iteration and clear
> clipboard, etc
>

Hmmm.... The Monte Carlo macro itself is dead simple and doesn't really
use any variables other than an integer index for the outer For/Next
loop. Other than that it just sets a few cells equal to the contents of
some others plus/minus a random delta. And then looks at the single
resultant cell to decide whether to keep these new values or not.

Buried within the spreadsheet code being used though are custom VBA
evaluation functions that set up fairly large data arrays and operates
on them. These functions are probably called 20 or 30 times for each
pass of the low content Monte Carlo routine itself. I would think that
these functions release their memory each time they complete execution
though.

I'll go through all the code again though with an eye to that sort of
problem. And thanks for the suggestion...

Somehow the act of XP moving it's focus among the various active
programs seems to trip up Excel. Like it's a memory management issue
perhaps. Maybe I'll send a copy of the sheet to a friend who has the
current version of Excel to see if it runs any more robustly on his machine.

Bill