>Good evening Ed
>
>Thank you for the information. We tested your solution here, and it worked. However, at the customer's site it did not work. We really aren't doing anything fancy with the escape code, just plain vanilla Courier fonts internal to the HP 4000. <1B>s0p12h0s0b4
>
>The ONLY thing we had to set here was the 10 cpi font. Nothing in Printer Commands. As I said, that is all that was required to get it to work here.
>
>The customer has a Novell and a Windows 2000 Server and has TCP/IP as well as SPX/IPX protocols bound the the Jet Direct card. (Here we are TCP/IP only), but I can't see how this could make a difference). We even cleaned out the Expr, Tag and Tag1 in a couple of .frx reports for testing at the customer's site and recompiled.
>
>Any thoughts?

The next thing to check is the video driver setting. It'sossible that they are running with Large Fonts rather than Standard Font sizes - that would tend to screw up screen layouts, but shouldn't have an effect on printed out (famous last words) but the printer driver and video driver do interact in the GDI.

Novell print queues and Win2K print queues behave very differently as far as how they handle print streams fed to them - the Win2K server's print stream is filtered through the GDI of the server, while Novell provides no direct driver handling, relying on the workstation-resident print driver entirely. You might want to try switching the printer to a Win2K station and using it from its share to see if that has any effect; I'm only guessing here.

You might want to look at the dot resolution of the two Generic/Print Only text drivers in use; if one is significantly different than the other, I'd investigate setting the YRESOLUTION and PRINTQUALITY settings to lower values in the EXPR memo. I'm pretty much out of altitude, airspeed and ideas here.

>
>Thanks
>Donald Lowrey