>That's just it...there is code needed for the report (the new apps pointed to by the _REPORT* variables) that will run outside the COM+ environment. This may not be the best example, but the one that comes to mind... it's like have managed and unmanaged code. Managed code is recommended and should be used. If using unmanaged code, you have to be careful about what you're doing. With VFP reports, we don't have the option of running them inside COM+. We should be able to pick the best technology and solutions for our customers. Here's a limitation that may prohibit that.

It appears to me that you may be asking for something you really don't need in a solution. In fact, holding a REPORT FORM command exuection within an MT DLL via COM+ may not be the best solution here. I don't know what you mean when you say something is recommended and should be used. There is no blanket generalization to use managed code or COM+ just for the sake of using it. If you have very specific VFP code or a detailed scenario that shows some hinderence or lack of functionality not being able to do this, I'd like to review it. It is possible that holding up an MT DLL with a REPORT FORM rather than spinning it out to an out of processes execution of it is a better solution even if you could run REPORT FORM in an MT DLL.