>Well trace the code to the point where the report starts printing. See if the program hangs the same time of the delay. You might also try to issue a "set printer to" command right after the report. Also try playing around with the report form command - like adding a prompt command or removing one.
>John Fabiani

I don't think that it's problem of program code. Another program written in old DOS clipper runs exactly, i.e. with printing delays.
What's wrong with databases programs like Clipper DOS and Foxpro for DOS in Windows NT 4.0 and printing on dot printers