Craig,
I would like to respectfully ask you to abstain from technical information in this thread and keep it only for personal attacks <g>.
>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.
>
>
>>
>>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.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
