>I think you're missing the point here. The EXE will still not run under COM+. It's limiting the advantages of running COM components under COM+. IMO, it's a serious limitation.
>
>>
>>I assume you can set up a queue so that a table is updated and a COM EXE monitors that so that reports are executued when needed, even if an MT DLL is the one making those requests. Or some work around such as this to allow you use MT DLLs and the VFP 9.0 report engine in one solution.

I don't see how this is a limitation when you can farm out the task of running a report outside of a COM+ environment. The printer itself is not part of the COM+ multi-threaded processes, but when you send stuff out to the printer you continue on and let it run independently. You can do the same with the REPORT FORM command, as it does not need to be within the MT COM+ environment to execute, and your app/components can continue on as needed.