>>>From VFP9 help: "REPORT FORM and LABEL commands are no longer automatically prohibited as user-interface-related commands in COM objects compiled into DLLs, when you run the commands in object-assisted mode. The restriction still applies to these commands when they are run in backward-compatible mode. (The topic Selecting Process Types explains why user-interface-related commands are prohibited in DLLs.) This change is not applicable to multi-threaded DLLs".
>>
>>Hi Sergey, Thanks for the reply. I take it that the Reporting can be used from within the DLL. I just have to use the VFP9 functionality.
>
>Only in STDLL, not MTDLL.

I am using _REPORTOUTPUT System Variable = ReportOutput.app to create the report output. While in a standalone program ran from within VFP9, the line:

DO (_REPORTOUTPUT) WITH HTML_Listener, loHTMLRL

returns a valid object to loHTMRL, it returns a NULL when called from a DLL. Looking further into the problem, it is noted in the _REPORTOUTPUT Requirements that:

"It must be modal, because it must provide an appropriate reference back to the Report Engine. If it provides any user interface elements, for example allowing the user to select an appropriate ReportListener from a list, this interface should be modal as well."

My goal is to print graphics (data-driven, think of something like a graph) from our existing applications - which are compiled in VFP8 - using a VFP9 DLL. Is this a dead-end approach?