>Thanks. This is an important requirement for me, since the user wants to abort the system if the printer is not ready. Any ideas?

Others have already mentioned that functions to return the printer status are not to be trusted. It is also possible that the paper jams - after the printer starts printing.

You can ask the user whether the printjob was completed successfully. There should also be options to change the mark, of a "printed" job, to "unprinted", or to somehow print a job again. In Bata/Bolivia, in one report I had to include an option to print additional copies of a certain report - but the additional copies were marked as additional copies, as part of the report. Since it was possible that something happened to the original printout, we also had to include the option to take away the "already printed" mark, as mentioned above.