>I have a clint running a custom app that is now experiencing random problems with check runs. Every now and then, the first few checks (2 to 5, so far) never make it to the printer. There is a single table that feeds the check report form, there is no filter set, and the table shows that all checks were printed; yet sometimes the first couple of checks never make it to the printer. The table typically will contain 10 to 15 checks, so we're not talking hudge print jobs.
>
>The SET PRINTER TO CHECKPRINTER command is the line before the REPORT FORMAT checks.frx TO PRINTER NOCONSOLE command.
>
>Is it possible that the set printer command is taking too long to happen on the network (the check printer is a network printer) and messes up the spooler?
>
>I have spent 20+ hours looking at code and trying to replicate this in my office and cannot.
>
>Any suggestions would be greatly appreciated.
>
>Dick Day

SET PRINTER TO NAME CHECKPRINTER
REPORT FORM ...

What happens if you just put a prompt in the report form command. I don't say you do this in your final version but for test.

REPORT FORM checks.frx TO PRINTER PROMPT