Claude,

I don't know if this is implemented yet, but there is a good change that it is -- I didn't know that was in the docs and so have not tested it. I suggest that you go ahead and try it. The language in many of the "design documents" such as you are quoting from is often in the future tense because it was written many moons ago as a road map for the VFP developers.

>This looks promising, but, does it mean that it's not available in the Beta or should I be able to test now:
>

>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).
>
>We will recommend that SYS(2335,0) still be used to trap for any modal
>states such as an Open dialog occurring if a data table in the report’s data
>environment is not found.
>
>If the ReportListener executing in a COM server finds that it is set to
>ListenerType 1 (Preview), it will automatically switch to ListenerType 3
>(all pages rendered at once, no REPORTPREVIEW.APP invocation).
>
>Quietmode will default to .T. for all COM states.
>
>The new-in-VFP9 SET TABLEPROMPT OFF feature may be useful to people using
>REPORT FORM commands in COM objects as well.
>