Thanks George,

I will take a look at the article and give it a go. Will post a message back here later if I get a resolution to this (and even if I don't).

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.
>
>I've run across a KB article that might be of help, Q175083 ("HOWTO: Print Line-by-Line to a Printer"). While it's in VB, it'd be a simple matter to test since all the source code is provided and it can be copied and pasted as required. My thought here is that perhaps this might emulate how VFP does it's printing. It occurs to me that one major difference between VFP and an application like Word may be the fact that in Word, the document already exists, while in VFP it's generated at runtime. This is a pure SWAG on my part, but if you got the same error in the VB simulation, it would pretty much nail the driver as the culprit.