Lisa,
Thanks for your help. We've been able to do 'REPORT FORM ...' from VFP COM EXEs for a while. As a matter of fact the current workaround for doing 'REPORT FORM...' from a vfp MTDLL is just to create a VFP COM .EXE, put the REPORT FORM in there and call that method from the VFP MTDLL. This works in vfp web services and vfp web applications but is sort of clunky.
If we could do the 'REPORT FORM ' directly in the mtdll, it would be an improvement.
The following text from the new Docs seems to indicate this capability will now be in vfp mtdlls:
1.2.2.7 Changes to COM behavior for Object-Assisted Reporting
Object-Assisted Reporting makes REPORT FORM-based output an appealing scenario for B2B data translations, HTML output on the web, etc. To facilitate this extended use of REPORT FORMs, we will change the behavior of the REPORT FORM command in COM servers as follows:
REPORT FORM will not be disallowed as a user-interface command automatically if the REPORT FORM is executing in Object-Assisted mode (a Listener is used to Render).


>David, as far as I knew, although that might well be a "on the table" in this thread <s>.
>
>Also "printing" wasn't under discussion. The REPORT FORM command was under discussion <s>.
>
>Whether the restriction for REPORT FORM is lifted, whether printing is available, and whether MT is available for REPORT FORM are three separate questions.
>
>I have responded to the thread based on one question, which was in the title of the thread.
>
>I will clarify the other two as soon as I can, and I hope that's good enough for you for now.
>
>Frankly once it is clearly specified that REPORT FORM is not available in an MT DLL I am not entirely sure why having it available in a COM DLL versus a COM EXE is such a "core question" but I will do my best to satisfy your curiosity.
>
>>L<