>Question: I didn't mention that each program (2 from each workstation) polls MyCom.EXE every second. Will MTS delay response back to the workstations?
>

Remote access of the COM server will introduce a significant delay compared to local out-of-process access, since each call must be marshalled across the wire to the server twice - one request inbound to the remote server, and at least one reply outbound back every time a method or property is referenced, so traffic over the wire introduces delays. And then comes the issue of servicing 40 requests in parallel - an MTDLL runs on a single processor instance. In general, MTS managed objects need to be stateless - they do not rely on the server maintaining the context of itself relative to each session, so in general, more information will need to be passed for each method call to reestablish the context of a transaction.

I doubt that the issue of MTS will be as great as the communication latency and added cost of establishing or maintaining states. What does the COM server do that makes execution on the remote server attractive?