Andrus
If the output is always txt files, why don't you use TEXTMERGE method instead of REPORT FORM to create the file? You can achieve a nice control over text output with \ and \\ commands.

HTH
Jaime

>I use a number of reports as templates to generate txt files using
>Those repors contain one field in each row with plenty of empty space
>between rows.
>
>I use the following command to create txt files :
>
>_ASCIICOLS=250
>REPORT FORM TO FILE ASCII
>
>In Windows 98 this works OK.
>In Windows 2000 some lines in output txt files are merged together in random places: first character in sime line is replaced by a first character from a second line.
>
>I realized that this is a VFP 7 bug. Since Microsoft will not fix VFP 7 bugs I'm looking for another solution.
>
>This solution must allow non-programmers to create a report templates and utility to generate a txt files from them.
>
>I'm looking to the following possibilites:
>
>1. Is it possible to modify frx2word so that it will generate txt files without using word ?
>
>frx interpretation and Word automation code is mixed in frx2word.
>
>There seems to be two possibilities: a) re-write frx2word separating word automation into separate class. This allows to add new drivers to frx2word to generate txt and html files.
>
>b) modify frx2word code to add txt file creation.
>
>Is this reasonable ?
>
>2. Is REPORT ... ASCII bug fixed in VFP 8 ?
>
>3. Or are there some free other solution ? I studied a txt file creation utilities in file area but have'nt found any utility which converts frx to txt file .

Why do programs stop working correctly as soon as you leave the Fox?