Good catch, Andrus. What I found there serves to avoid whole columns of data that become blank if they are not saved in that order, especially after migrating reports from DOS which results in overlaping report fields.

The last couple of days I have been working on disappearing rows or inserted blank lines. I am approaching it by searching for "magical numbers" as Naomi said. Specifically, by programmatically increasing the width of report bands by tiny amounts until the results are just right. I have had good results, but nothing generic, unfortunatelly.

Alex

>In the thread
>
>REPORT FORM TO FILE xxx ASCII discovery Alejandro Sosa 14/02/2006
>Thread ID: 1096211 Message ID: 1096211
>
>you wrote:
>
>I think I found an answer to the age old problem of mangled columns
>when using REPORT FORM TO FILE xxx ASCII.
>
>In summary, the fields have to be stored in FRX in right to left
>order. Here is code to do that.
>
>I have found that this corrects report to asci issues.
>What other issues do you have?
>
>

  SELECT *, ;
>  	  ICASE( INLIST(ObjType,1,2,3,4,9,10), ;
>	         '1'+TRANSFORM(RECNO(),'@L 999999'),;
>	        INLIST(ObjType,5,6,7,8), ;
>	          '2'+TRANSFORM(999999 - HPos,'@L 999999'), ;
>			'3'+TRANSFORM(RECNO(),'@L 999999')) ;
>				AS cOrder ;
>    FROM oldreport.frx ;
>    ORDER BY cOrder ;
>    INTO TABLE newreport.frx ;
>    WHERE platform='WINDOWS'
>