George,

Oh, for cyring out loud.. You guys are being way too nice to each other. *g*

What about a "pre-print" squirt to the printer? Only thing there is you would most likely lose a piee of paper unless you could somehow figure out a way to send one character to the device, have it not eject the page but return a code (error or no) and if all's ok proceed.

Not too practical but perhaps it will spark your fertile mind. Kind of like a match and a far*. *bg* & *gr&rvvf*

Best,

DD


>>>Yes, it did, thank you. And I hope your's was the same.
>>Yes, very nice, thanks.
>
>You're welcome.
>
>>>>>Always glad to hear another opinion< g >.
>>>>Well, I don't know how useful it is, but I will soldier on < bg >
>>>Ah, c'mon. Hearing another opinion is always useful, IMO.
>>
>>Well, what's that thing about a 1000 sets of eyes makes all problems shallow :)
>
>Well put!
>
>>>My thoughts exactly.
>>I thought maybe that was what you were getting at when you said you can't make it the application's responsibility, but I wasn't sure, and that is why I posted.
>
>No need to explain.:-)
>
>>On a slightly un-related note, we do get to find out when something is successfully printed yes? Isn't that the spooler notifications that can be set to pop up (at least under NT, I don't know about 95/98 how this works). Do you know how to tap into this information via the API? I don't know if it would help with finding when it didn't print, but if nothing else, one could queue receipts internally, and remove them when the spooler notification is sent.
>
>Since I don't use NT (I am shortly going to be switching to Win 2K however), I'm not exactly what you're referring to here. It doesn't sound like anything available under Win 9x, but there could be something I'm missing here. It would seem, however, that making VFP aware of this action would be the same as the printer thing.
>
>One of the reasons (there are many) I'm switching is to familiarize myself with NT functionality and its API. I just can't stay 'way from this low level stuff.:-)