Time Hog
 

Using Excel 2003, I have a VBA program that I use to do Monte Carlo
analysis. Sometimes I run it for an hour or two. My one gripe with it is
that it hogs the whole machine and makes it difficult to use other programs
in the foreground. Generally I run it at night and don't care, but
occasionally I need to run it during the day.

Is there some way to tell VBA to limit the machine time it burns -- to force
it to pass off XP's multitasking off to the next task? Or to tell XP-Home
to limit how much resource gets allocated to Excel?

Thanks.

Bill

Time Hog
 

"Bill Martin" wrote in message
...
Using Excel 2003, I have a VBA program that I use to do Monte Carlo
analysis. Sometimes I run it for an hour or two. My one gripe with it is
that it hogs the whole machine and makes it difficult to use other
programs in the foreground. Generally I run it at night and don't care,
but occasionally I need to run it during the day.

Is there some way to tell VBA to limit the machine time it burns -- to
force it to pass off XP's multitasking off to the next task? Or to tell
XP-Home to limit how much resource gets allocated to Excel?

Thanks.

Bill


Good point Bill if there is a way to partion processor usage I would love
to know about it too.

My two machines are falt out looking for new Mersenne primes and it woul
dbe nice to continue to do so without interuption and yet work with macros.

N10

Time Hog
 

You could try putting a wait in the code somewhere. Though this will
probably cause it to take 2 days to run, as well as possibly cause
other adverse affects. So basically...I have no idea, but would like
to know as well. =)


N10 wrote:
"Bill Martin" wrote in message
...
Using Excel 2003, I have a VBA program that I use to do Monte Carlo
analysis. Sometimes I run it for an hour or two. My one gripe with it is
that it hogs the whole machine and makes it difficult to use other
programs in the foreground. Generally I run it at night and don't care,
but occasionally I need to run it during the day.

Is there some way to tell VBA to limit the machine time it burns -- to
force it to pass off XP's multitasking off to the next task? Or to tell
XP-Home to limit how much resource gets allocated to Excel?

Thanks.

Bill


Good point Bill if there is a way to partion processor usage I would love
to know about it too.

My two machines are falt out looking for new Mersenne primes and it woul
dbe nice to continue to do so without interuption and yet work with macros.

N10

Time Hog
 

Nowhere have I found a satisfactory answer to this issue. The best I've
come up with is that if one has a multiprocessor machine, I *think* you can
force Excel to run on one processor and other stuff on the other. I haven't
been able to verify this since I lack such a machine, but that's the only
thing I've come up with.

Bill
----------------------------------------
"John Fuller" wrote in message
ups.com...
You could try putting a wait in the code somewhere. Though this will
probably cause it to take 2 days to run, as well as possibly cause
other adverse affects. So basically...I have no idea, but would like
to know as well. =)


N10 wrote:
"Bill Martin" wrote in message
...
Using Excel 2003, I have a VBA program that I use to do Monte Carlo
analysis. Sometimes I run it for an hour or two. My one gripe with it
is
that it hogs the whole machine and makes it difficult to use other
programs in the foreground. Generally I run it at night and don't
care,
but occasionally I need to run it during the day.

Is there some way to tell VBA to limit the machine time it burns -- to
force it to pass off XP's multitasking off to the next task? Or to
tell
XP-Home to limit how much resource gets allocated to Excel?

Thanks.

Bill


Good point Bill if there is a way to partion processor usage I would
love
to know about it too.

My two machines are falt out looking for new Mersenne primes and it
woul
dbe nice to continue to do so without interuption and yet work with
macros.

N10