Michael,
What do you mean simultaneous connections to Excel? One application, multiple worksheets?

FWIW, I tried something similar with a web application. I was using WWWC and I hooked an Excel object off the main server object. The problem I kept running into was the application would lock up. Since it was a DCOM object, I assumed an error occurred and the dialog tried to come up and failed. When I started creating Excel objects on the fly only when I needed them, all my problems went away.

>Thanks for getting back to me, Larry. It took a while to respond, as I was doing more research on this problem. The article to which you refer does not seem to apply, however I think I found the problem, and this is more of a question, too.
>
>I'm using Excel 2000 on my development system, and the client has Excel 97. My program was setting up two simultaneous connections with Excel, and it appears that Excel 97 experiences some kind of a conflict with this. Even though I am indeed fully-qualifying the Excel object, there will appears to be conflict.
>
>Therefore, my question is: Is there a difference between Excel 2000 and 97 that would cause this sort of difference concerning multiple connections?
>
>This is the only cause I can think of for my program's errors, but the client has not tried out the update yet. However, there were two different processes taking place with Excel, one used one connection at a time, and the other used two connections at a time. It was with the multiple connection process that the client was having trouble. I changed the mutli-connection to a sequential connection, and am awaiting feedback from the client.
>
*snip*