Hi Marat
It is impossible because the reports use global aplication manager object The object stores for example customization parameters called in reports.
The reports are indeed not usual - because - I did not use their private dataenvironment directly - in init method of dataenvironment (autoopentables=.f.) I render it, I read view and tables properties and on this base I create and fill cursoradapters that contains the same data and have same aliases. Using the way with cursoradapters I can switch datasources between VFP DBC tables and SQL Server tables without need to create additional remote views or use SPT and without need to rewrite reports for adding SQLServer backend. In most cases all I need to do is to add few line of proper code in init method of report. I choose this way because my apps have many reports created with local data in mind and I wanted to use the reports with SQLServer changing them as little as possible. If you promise that I will have errorless PDF output also in case of such reports - I will try XRFX.

>Hi Josef
>I would like to test your "not simple" report with FRX2Any. Could you provide me that report?
>
>Thanks
>
>>Hi, Craig
>>I believe that VFP9 will be backward compatibile and that is the reason why >I wanted to have PDF output option included in VFP box. My trust in future >additional applications made by 3-party is very limited - this is based on >my expierience while evaluating tools that render VFP reports definition (not simple) to make PDF output. Maybe the Ken mentioned hooks will help >made such add-on. But today I have no warranty that such products will >exist and that they will make proper PDF output for my reports.