Hi,

On this issue, I facing the same problem of getting status from the printer.
This is especially problematic for me since my application is a kiosk application. If only we had some solution to this issue. I be glad and
save me some sleepless night. I am not getting much help on my OPOS
driver. If you know anything about it, please advise. Thank you


>>If you're accessing the printer directly, as Elmer mentioned, yeah, it'll happen. Of course, I stopped doing that mmm...about when Win3x came out. It just didn't make sense with the various combinations of printers etc. While we may not like it that much, I think letting the driver handle things like the printer being off line or out of paper, or off completely, makes life so much easier and takes some of the complexity of development out of our hands.
>
>Hi George,
>
>I also rely on the print driver to handle the printer and do not access the printer directly since I can't remember when, but I still run across this every once in a while when a customer has a problem printing a report when "all other applications print just fine". This occurs when someone turns off the print spooler in the printer setup which is still one of the options in all Windows version up to WinXP Pro. I have only seen this happen with FPW 2.6 apps and have not run across it since using VFP, so this may no longer be a problem. I always thought that perhaps when the print driver is set to send directly to the printer, Foxpro may overrun the printer causing an error.