Al,
In order to make a DOS program print immediately, you have to force Windows to "see" the print job. The way you do this is to issue a command that creates an interrupt. I did this by issuing a !REM>NUL command right after the REPORT FORM... statement.
HTH
>>I'm just starting to look at some legacy code for a client and one of the problems their having is that the printer will only print when the app is shut down. They choose to print, nothing happens, then the printer kicks in as soon as they exit. The developer before me told them that that's just what they would need to do to print any reports...like it was a feature. Man, I Love those kind of developers! :) Anyway, it doesn't really sound like a Foxpro printer issue to me, per se, but could there be something on exit that forces a buffer or something to clear? The client said it used to work at one time. I won't have the code for a couple days, but I wanted to at least get some ideas in the meantime. Thanks!
>
>If it's NT/W2K look at LPT_Timeout in
http://support.microsoft.com/support/kb/articles/Q102/0/59.asp>
>If Win9x, look at
http://support.microsoft.com/support/kb/articles/Q140/0/36.asp