>Rauh,
> Then how to test whether the printer is ready? I need to test it before I print a report or else I notify the user that the printer is not ready.
>

You'll need to write a significant amount of code to access the port directly in C or another language with better low-level access to test things, or you'll have to not use the VFP print capability. You need to interact with the driver, and the driver doesn't actually detect an error in advance of it happening - I can take all the paper out of my inkjet printer, and Windows can't tell that I need more paper until I try to print to it, and the driver detects and responds to an error. THis gets even more complciated in network environments, where your local spooler doesn't have any direct link to the printer; in a pooled printer scenario with a network printer, where any of several printers might be trying to print the output for you, you don't even know the right machine to check!

The alternative is not to use VFP's printing capabilities, and try to handle the print port directly through API calls; not something I'd rcommend for general printing applications. This is one reason that my own apps that handle some form-oriented label printers handled printing through a COM object rather than sending print output to the printer via native VFP print methods.

>
>Harry