Tracy,

>So far this works the best but it's still not acceptable. I like how it prevents the page ejection though. If I use REPORT FORM TO FILE ASCII it creates the text file and the copyfile API copies it to the printer but it drops off data somehow. This is still that pesky bug where using REPORT FORM TO FILE ASCII drops column headings. If I go in and look at the .txt file the missing data is NOT there also.

Tracy,

I'm new to this thread, so please forgive any unintentional redundancy.

Have you tried experimenting with the values of system vars _ASCIICOLS and/or _ASCIIROWS to see if that solves your data cutoff problem?

The way those work, particularly _ASCIICOLS, is pretty baffling and is not always logical (at least is not always intuitively logical). Try some oddball settings like 40 or 50 for COLS, as well as larger than the default and you just might hit a combination that works. Also, different settings for ROWS might make a difference.

Or, perhaps the problem you are seeing with column headings is not related to that at all. I just know that in testing a couple of years ago, I found that the settings I tried that seemed less likely to be right actually helped with the spacing of data on the page.