The real problem is that even if your app successfully sends invoices to the printer, those invoices are in the printer's buffer, and may not be printed. Even if your app somehow flagged the invoices that were sent to the printer, that's no guarantee those invoices were actually printed.

What I've done in cases like this is to offer the user an option to re-print previously printed invoices. This option either allows them to specify the invoice number to start from, or shows a grid with all the previously printed invoices, with a check box by each, so they can select which ones to print.

>Hi All,
>
>I'm working on an upgrade of a clients application (FPD2.5b to VFP6.0) that produces a large amount of printed invoices ( up to 8000 pages ). The FPD2.5b application would create the invoices as a text file and then print the text file. This was done so that if a printer problem occured then the invoices that were lost could be reprinted. The Invoices in the VFP6.0 application are printed from report forms with a large amount of lines, rectangles, bold fonts, etc so can't be printed to a text file. The VFP6.0 application will be running on a W2K network either on a Lan or Terminal Server. One of the options I've looked at is sending the report output to PDF then printing the PDF, that way if there are problems with printing then the user can open the PDF and print any invoice that was missed, but I'm wondering if it's feasible to send large amounts of report output to a PDF. Does anyone know of a reliable way to ensure that reports sent to the printer will be printed even if the
>printer has problems?
>
>Regards,
>Gavin.