Hi,

I've been running some VBA in Access to open Excel and perform a number of
operations. In the past, it has always been the case that while the code is
running you shouldn't click the mouse anywhere or change the open window to
avoid generating an error. However it is suddenly working so that you can do
whatever you want in any open application and the routine will continue,
which is extremely useful. On transferring the routine to another PC it
works in the old way. How do you set this behaviour up to occur?!

TIA,

Rob

"Robert Chapman" wrote in message
...
I've been running some VBA in Access to open Excel and perform a number of
operations. In the past, it has always been the case that while the code
is
running you shouldn't click the mouse anywhere or change the open window
to
avoid generating an error. However it is suddenly working so that you can
do
whatever you want in any open application and the routine will continue,
which is extremely useful. On transferring the routine to another PC it
works in the old way. How do you set this behavior up to occur?!

Hi Rob,

Hard to say for sure what the difference is, but one thing that allows
this in Excel is if you have a newer PC with a CPU that supports
hyperthreading. With hyperthreading enabled Windows has a lot more
flexibility to switch among running applications because the single CPU acts
sort of like two separate CPUs.

--
Rob Bovey, Excel MVP
Application Professionals
http://www.appspro.com/

* Take your Excel development skills to the next level.
* Professional Excel Development
http://www.appspro.com/Books/Books.htm

Hi Rob,

Hard to say for sure what the difference is, but one thing that allows
this in Excel is if you have a newer PC with a CPU that supports
hyperthreading. With hyperthreading enabled Windows has a lot more
flexibility to switch among running applications because the single CPU acts
sort of like two separate CPUs.

That would make sense but the PC it works on is old and the PC it doesn't
work on has just been purchased! Could there be some kind of hyperthreading
setting in Windows? It really seems like there must be a setting somewhere
for it to have switched from one behaviour to the other...

Rob