Borislav,

You don't need to evaluate the fields before you run the conversion, XFRX should be able to call your UDF.
Is eLang a table field or a variable? Please be aware that XFRX for VFP 8 and older versions doesn't handle local variable used in reports. The workaround is to delare these variables as private.

Could you please try generating the log file:
Before calling SetParams(), please add loSession.initLog(). Then, when you run XFRX next time, _XFRX.log file will be generated in the default directory. This file logs all errors that are trapped during XFRX execution and could help us to find our what's wrong.

You can contact me directly at eqeus@eqeus.com.

Martin Haluza

>In my VFP report I have fields with some UDF in it i.e.:
>
>

>** Field Expr.
>
>GetlangVal("ID", 4, eLang)+" "+CursorForReport.Id
>
>

>
>Now I try XFRX to decide if We buy it. When I Print Preview everiting is OK, But when I try to export the report in other format (no metter what) for that field .F. appears instead of evaluating value of that expr. Is there anyting I can do or I must hack the FRX & evaluate the fields BEFORE I run XFRX?
>
>***** Update
>But When I remove function, everithing is OK. I have SET PROCEDURE TO Utils.PRG (where the function is stored) before I run report.
>

>** Field Expr.
>"ID "+CursorForReport.Id
>

>
>
>TIA.