The problem shows up both on my server and on my laptop that runs as a "development server" so I have the issue in two different environments. I have tried looking at timing, and that is one reason we have it in sequence so we dont close anything until excel is finished. for example one of the things removed in the test vi, was a call to run a rather extensive macro, so I know we are not trying to close down while that is still executing. also when the vi stops running you can see a drop in memory that excel is using, but it still stays open. Its almost as if its retaining it in memory in case it is called again write away, so it will open faster on the next execute, but if that were the case I would expect it to release at some point, and it doesnt.
I hope this clarifies thing a little bit.
Chris
