>I am using Foxpro/Lan 2.0 (I know it's old!) I have some users who only need one or two pages of a report so they turn off their printer after printing the pages they want. The Foxpro message "Printer not ready Retry?" comes up but when No is chosen the print job isn't always canceled, sometimes the "Printer not ready Retry?" message box comes up again, sometimes three times, before choosing No works. There wasn't any error trapping in the

You don't need error trapping for this. I've had similar (and other) printing related problems, so I wrote a trick for this: always print to a file, then FOpen() the file and send it in chunks to the printer (my chunk remained at 1K or 4K - and I've tried to print it line by line, but that was an overkill, and besides, didn't distinguish between lines ending with cr+lf and cr only), and check for printstatus() between any of the blocks. Then if it returns .f., I wait 20 seconds, and issue an alert ("Printer not ready: wait for it / give up printing").

This solved for another issue: once the printout was in a file, I could actually offer them partial print (page range, or search for a string and print n pages after that), so they could easily print pages 1 to 3 or 37 to 42. I still use it (in FPD2.6, using lots of functions from FPath.plb, but they may be emulated, and I still have an older version somewhere), so e-mail me if you need it.