Assuming that you are not trying to develop add-ins or WBs that are open/in
use in the initial instance, it should not be a concern what another
instance is doing.

NickHK

"Tim" <tim j williams at gmail dot com wrote in message
...
I've always understood that two different Excel *instances* (not just
workbooks) are completely independent in terms of macros and any other
aspects - ie. there is no "cross-talk" between different instances of the
application...

Anyone know different ?

Tim



"excelvbauser" wrote in message
...
Thanks Steve,
The scripts do not have activeworkbook nor activeworksheet. However,
they do have `thiscell' which could be causing the problem.
I will try to think of a way to launch a second excel fully
independent
of the first.

Thank you again


"steve_doc" wrote:

Hi

From your explanation I suspect that you macro uses the
ActiveWorkbook/ActiveWorksheet syntax?

If this is the case, there will always be conflict opening another
workbook
, as the new workbook is now the active workbook/worksheet.

There might be a way, but as yet I am not aware of it

HTH

"excelvbauser" wrote:

Hi,
I regularly run lengthy macros on excel 2007(that take about 20
hours at
a time). However, I have found that when I open a new excel
application on
the same computer(I have a dual processor pentium with 2 gigs of
ram) -
with
the intention of developing new macros on completely new sheets -
then
the
macro I was originally running gets hung up and never finishes.
When I run the original macro, it is only using one processor.
So, is it possible for me to open a second excel application that
specifically uses the idle processor, without disturbing the original
macro
which is running on the original processor? That way, I can develop
new
macros while the old runs are running. (as it stands now, I can not
run
macros and develop at the same time)