I call the following code to print to a generic printer on lpt1:

*** Begin
SET DEVICE TO PRINT
@01,01 SAY "This is a test print"
@50,01 SAY "End of the print test"
EJECT
SET DEVICE TO SCREEN


SET DEVICE TO PRINT
@01,01 SAY "This is a test print (2)"
@50,01 SAY "End of the print test (2)"
EJECT
SET DEVICE TO SCREEN


SET DEVICE TO PRINT
@01,01 SAY "This is a test print (3)"
@50,01 SAY "End of the print test (3)"
EJECT
SET DEVICE TO SCREEN
*** End

The problem is that the last page does not get printed. Instead, it sits in the print queue, "spooling" forever and ever. Only when I run the program again will the last page print. But, the last page of the next printjob does not print! In fact, the next printjob gets "attached" to the first printjob. It does not produce a new printjob in the queue.

Any print jobs that come in behind it (say from another person or application) get backed up in the queue waiting for my foxpro job to finish. Only when I exit foxpro (or the .exe) will the print job dump the last page and end the job to let others print.

Is there a special code that I need to issue to tell the printjob that it's done? Or do I need to do something totally different. (Prefer not to since it is old code and we are not converting it to visual yet). The code we are remediating is old QuickSilver code. We are bringing it to VFP5 because the client no longer has quicksilver licenses.

Any ideas?

Thanks for your help!

Jeff