>Thanks for your input. Do you suspect that sending an Escape sequence to the printer might resolve the problem? I do know the sequence for setting the page length for the printer.

Yes, if you're writing to the printer as a Generic/Text-Only printer, so that Windows doesn't try to interpret the print stream. In most cases I know of, where the printer has continuous feed paper and the pritner will accept a page length definition, it'll track and respond to a form feed to kick out the balance of the page length according to where it though top of page was. With a page-oriented device and non-continuous (separate pages) paper, it may perform the form feed relying on the feeder mechanism, and just force the next piece of paper in.

You also need to ensure that Windows doesn't send anything to restore the printer state before and after each print job, or setting the printer form length won't help.

If you want to send control codes, you're giving up hardware independence, so you might consider using a custom-defined page size in the Windows Control Panel, and using native fonts in Report Writer. My take is that the minute you want any lower-level control of the printer, you need to give up on Windows report writing tools and send raw print streams.