Question

I need to print PDF’s generated in an asp.net application using crystal reports. Upon printing, a database table gets updated with the status ‘printed’. How do we handle situation where let’s say, the printer runs out of paper?

I know this is on client-side, so what’s the right way to handle issues like this?

TIA

Answer 1

The printing is done client side and handled by the users machine, you will NOT have access to this information.

Expanded Answer

To expand upon the comments. The process flow that happens for this type of thing is as follows.

1. ASP.NET Sends the file to the client (You control)
2. The browser opens the file with the client’s default application (Browser Controls)
3. The default application displays the file (Application controls)
4. The user opts to print the document, maybe now, maybe 3 days from now (Application Controls)
5. The application sends the request to the printer and is done (Application Functionality)
6. The printing systems actually print the document, if a failure IT notifies the user (Printing system control)

So, as you can see, not only are you once disconnected from your ASP.NET application you are actually outside of Acrobat if you want to get a “True” did it print result. For example if you print a document in Microsoft Word and the printer runs out of paper, who notifies you? Not Microsoft Word but the print spooler system.