Alex,

I've had some success with REPORT FORM TO FILE usage by making a second copy of a report (Save As...) and changing to a monospaced font (Courier New, FoxFont, etc. see http://fox.wikis.com/wc.dll?Wiki~MonospacedFonts~WIN_COM_API). A bit of tweaking produced more reliable and predictable results. That might be easier than hacking the FRX on-the-fly.
________________________

>>>This is an old question that many of us have had trouble with.
>>>
>>>The question is how to REPORT FORM TO FILE ASCII correctly a VFP report. In the case of reports designed with FoxDOS and kept in the FoxDOS format, VFP creates the output to file correctly, but in the case of reports that I migrated programmatically from FoxDOS to VFP format the results are unreliable. These reports print and display correctly but when it comes to creating an ASCII file there are problems. I have tried to programatically space report elements farther apart vertically just before issuing REPORT FORM TO FILE ASCII, including increasing band size, but sometimes a line is totally skipped and some others a field and a label are printed in separate lines. The difficulty could be dealt if I knew exactly the rules used by VFP to determines break between lines. Does anyone have any idea what those rules may be?
>>>
>>>I use XFRX which does a fine job creating pdf files. In that case I think it is writing pixels to a file, which is not the same as outputing whole characters. XFRX also has similar problems creating text files.
>>>
>>>Alex
>>
>>Can't you keep the old FoxPro/DOS report, without converting? That should cause you much less headache.
>
>That is what we are doing now, but it is a pain because all maintenance has to be done using FoxDOS. I am trying to finish the transition.
>
>>Or, use some other alternative to generate text files, such as my download #9991.
>
>If I recall correctly the limitation to your method is that it does not allow visual design, correct? Or is this a different one?
>
>I would like to find a way to open the FRX file and modify it on the fly just before issuing REPORT FOR TO FILE ASCII in such a way that it creates the ASCII file correctly.
>
>Thank you for the response.
>
>Alex