I got tired of trying to make things fit with the ASCII clause, so I used @...say commands; later I found ?/?? to be more flexible. Eventually I ended up creating a special class for text reporting; now it supports text reports, and Excel reports.

If you are interested, a version is available as download #9991; the disadvantage is that you have to program the report specifically, instead of re-using your existing FRX files.

>Hi:
>
>I have a weird problem when exporting a report to a text file. I'd like to know if anybody else experienced this, and how it got resolved.
>
>****
>THE REPORT:
>It is laid out with a group header and a group of detail records for each header. E.g. CUSTOMER in the group header and INVOICE records in the detail.
>
>****
>THE PROBLEM:
>On SOME groups, the GROUP HEADER overlaps the first line of the details. It is like having no carriage return/line feed at the end of the group header line, resulting to the first detail line being exported into the same line as the group header.
>
>****
>HOW THE REPORT IS CALLED in code
>I do this via a command like the ff...
>
>REPORT FORM reportname.frx TO FILE export.txt ASCII NOCONSOLE
>
>I set _asciirows = 63 and _asciicols = 256
>
>
>Any information that sheds light on this problem is highly appreciated, and i thank you in advance.
>
>regards