Borislav, XFRX is a very nice product, but you have to try it with your oddest reports, those which push the limits of the VFP report engine. In my experience, for the rest of the reports it will work OK.

For example, I found two limitations: one of them is that you cannot change the database property of your cursor in the dataenvironment at runtime (a common technique if you have different path structures in your development machine and in the production machine). This can be solved modifying SET PATH so that XFRX will reach all the tables in the dataEnvironment (be careful if there are more than one copy of the databases in the production machine).
The other one is with execScript() in the dataEnvironment methods, and I have to ask Martin as to how to go around this one.

HTH,
Javier.

>Martin,I am veeery stupid today :o))))
>Because I Use Your Demo form to check XFRX with my most complicated report.
>When I test it with normal VFP preview I see there is CLOSE ALL clause. It clears SET PROCEDURE TO...., I fix it BUT ONLY form Normal preview. The same is for variables used in report i declare it ONLY for Preview :o((((
>So excuse me. I'll test some more & let You know if we buy XFRX.
>
>Thanks