Hi George,

I took a look at the article - it said in the intro that it would only really work on "line by line" printers like dot-matrix printers. I remembered then that I had written something to do something similar for another app a while back (it dumped a "binary" print file that had been captured to the printer).

On another note, when you mentioned winspool.drv, it got me thinking about the setup on this machine....spooling is turned off (because we print to network queues) and do you know off the top of your head if this means that the work does not actually go through winspool.drv (seems to me that it would still go through there but just wondering). Does this trigger anything?

Albert

>It occurs to me that one of the things that might make this happen is the way VFP interfaces with winspool.drv. VFP doesn't call the HP driver at all, it calls winspool which in turn calls the driver. This is more fodder for the argument that it's the driver and not VFP, BTW.