Clipper Errorsys and print Retries

[clip4ever]

Having a Clipper 5.2c Client/Server app, running on Win 95 W/S connected to Win 2000 server, and printing to Lexmark printer with Xerox Emulation, connected locally to W/S.
The problem is, with large printing jobs, printer would still be printing page 1 while app sending page 7. If the printer ran out of paper, we would not detect this on time to halt sending info to printer. Clipper detects out of paper, aborts the print command in the middle and displays a window with Break or Retry options. Retry will cause printing problem since Clipper re-sends the aborted command. The only solution we found is to print to a file first then issue a DOS COPY command from Clipper app to send the report to the printer. DOS COPY worked but is displays a DOS message for the out-of-paper message, which scrolls the Clipper screen up.

HAs anyone faced this problem ?
Is there a way to force Clipper to continue sending the same print command ?

Thanks

clip4ever

 

[mehrnosh]

Hi

The clipper.lib file has ERRORSYS.OBJ in which there is a function called Print_error u can extract the ERRORSYS.OBJ using tlink modify the function and put your own code.
U can refer to clipper by Rick Spence(who is the co-developer of clipper) for the original code of errorsys.obj

or
U can generated the output to a file using set print to filename and display it to the user and prompt for which page no. to start printing.
check out the link

http://www.clipx.net/ng/sum87/ng7e296.php

http://www.clipx.net/ng/sum87/

 

[clip4ever]

Thank you for the quick response. I actually tried these two solutions. What I was looking for is a way to tell Clipper to resume printiong where it stoped, which will prevent the problem. The DOS Copy would have been perfect with the DOS Spool set to On, in the printer setup, but this feature is not working properly on Win 95.
Thank you anyway.