The reason I use two instances of excel is that I create
charts of the data that is generated on the first instance
and during the day, I have to adjust them as the day
unfolds. If they (the charts) are in the same instance
where the data is being collected, it makes that instance
crash.

However, transmitting the collected data to a second
instance and charting it there, solves the crashing
problem since I am then able to manipulate the charts
without disturbing the vba processes in the first instance.

Make sense??


-----Original Message-----
But why 2 instances? Why not 2 spread sheets open in the
same instance? That
would be a lot easier to deal with...

"Coyote" wrote:

In my present setup - I am running two instances of
excel
and transfering data between the two via a huge pasted
link array; but have the idea that a vba program that
transmits the data a piece at a time would be more
efficient than the big pasted link.

That is why I am trying to figure out how to accomplish
the task I have been asking about. I figured if I
could
get that little part to work, then I could write the
macro
to accomplish the larger task.

But so far, I am unable to get vba in one instance to
see
the other instance.


-----Original Message-----
I've been sitting here just ~assuming~ the whole time
that Excel was
one of those application that didn't support multiple
instances of
itself running at the same time. But, well, sure
enough
I just
opened a second instance of Excel with two separate
process IDs.
Blushing. :]

The two instances are aware of each other though.
Instance 2 opened
with Book4 as the default workbook name, as I already
had
1, 2, 3 in
the first instance. I then created book5 in instance
1,
went back to
instance 2, created another workbook, and that created
as
book6.

But I think you're probably right about what's going
on.

Ray at work

"Jim Thomlinson"
wrote in
message news:5DE756F1-953F-4197-B8FB-
...
Just a thought but is Research.xls open in a
seperate
instance of
Excel. If
so then it is possible that although research is
open
that the
macro can not
see it...



.


.