That is strange - I havent seen that.

I have seen the .F. when the field you are printing is invalid (not named correctly or field not there).
Also, you don't get the .F. with VFP7, but you do with VFP9.

Cyril


>Hi Martina,
>It haven't used the init log in the past. I give it a try and see if that tells me anything useful.
>
>I'm using v12.6.0003 for XFRX. I haven't been using the reportlistener.
>Dave
>
>>>All,
>>>I'm using the XFRX report conversion tool from Eqeus. I have it integrated in my VFP application to convert reports to PDF, HTML, etc. I've been using it for years without issue, until recently. The problem that I've come across is that in certain environments the report conversion process completes but the info in the report is displayed as the ".F." for all data fields. When this occurs there isn't any error messages generated or issues with PDF file being display. It's just the content in the PDF report is nonsense.
>>>
>>>From my testing this appears to happen typically on Windows Vista and 7 OS where the UAC feature is turn on. If UAC is off, the report converts without issue. To confuse the issue further, the XFRX converter works (with UAC) if my VFP program is run from ShellExecute routine, but not when run from a shortcut or from the EXE program directly.
>>>
>>>Has anyone experienced anything similar in their apps. Moreover, it there a fix or a workaround?
>>>
>>>I've visited the Eqeus site but there's nothing there to suggest they're familiar with this particular issue.
>>>
>>>I welcome any suggestions or advice,
>>>- Dave
>>
>>Did you try init log for XFRX?
>>

>>local loSession, lnRetval
>>loSession= xfrx("XFRX#INIT")
>>loSession.initLog() 
>>* or method SetLogFile(tcLogFile, tlSilent)
>>...
>>

>>
>>The problem is at exporto to pdf on preview form?
>>Did you use reportlistener?
>>What version XFRX do you use?
>>
>>MartinaJ