Hi Nancy,

Thank for your advise on this issue.
I am one of those fox user that faces this problem.
I had look at this and post for help but didn't get any
good or workable solution on this issue. The window API
is not working at all, I had tried lot of way but don't
had any solution working.
As I am working on a kiosk product, detecting printer problem
is very critical to me, but I having problem using the OPOS
driver with my POS printer. Whenever, I set the DeviceEnabled =
.F., my system seem to halt and give illegal error and crash
my testing program. I am loss.

Is there way for VFP to read parallel port status of their
individual pin by address ?

I believe there will be some solution to our printer problem.
If you come across any solution, please kindly let me and other
know. Thank you


>>We have just discovered that neither sys(13) nor printstatus() work in VFP. Additionally, we have noticed that getprinter() and sys(1037), which both display the printer dialog box, do basically the same thing as the other two -- which is to indicate that the printer is 'ready' regardless of what its actual status is. I have waded through several of the threads about this issue, but have somehow missed the answer as to how one can actually determine if a printer is on line or offline or whatever. We would like to spare our users the dismay of getting stuck in a report and having to ctl-alt-delete their way out.
>
>I'm not sure why the users are getting stuck in the report. I just get a message when I try to print to an off-line printer. However, with regard to PrintStatus(), I had a gut feeling that it shouldn't even work. But I googled the subject and found this that applies.
>
>There are some printer and print spooler related functions in the Windows API here. Didn't see anything offhand that might apply.