I guess you have two issues here. To get rid of the blank paper, you must "eat" the form feed by routing it to a file

Set printer to file dummy.xxx
eject
Set printer to
erase dummy.xxx

The slow start of the printer is most likely fixed by adding SET PRINTER TO after the old code. Without this line Windows will think that more data is coming later, so it will wait for a specific time which you can see in the printer driver. Windows doesn't send data to the printer in small chunks like DOS did, instead it caches it and sends everything at once. By issuing SET PRINTER TO Windows will understand that you are done with your print job, and send the cached data to the printer.

>I can't believe I'm asking this question but I'm looking at code that is 20 years old and I'm lost. This customer has a function in a current program they have never used but now need. It simply prints a check to a dot matrix printer. There are two issues the first is the speed of the printing. From the time I initiate the print to the time the printer actually starts printing is anywhere from 45Sec to 1Min. The program is not using a report form but "Set Device To Print" and @ Say commands. The second issue is the length of the page which I think must be a printer issue. The check is 8.5 X 7 but the top stub information prints at the top of the page a full page is ejected and them the check is printed. I tried this from two different computers but the same printer. If I can get these two issues resolved everything else is working fine. It's just been so long since I've had to deal with something like this I'm not sure where to turn. Is this a printer setup issue? Windows XP issue? Fox 2.6 issue?
>
>
>TIA
>
>Jeff