Heya Jim -

sometimes stripping out ALL OF the encoding in the report field can have some nasty effect as well, as you've found with the concept of proper tray selection.

What I've done in the past is stick with a pcl driver for hp that
had pcl5e and then hack on the tray select coding , stuffing what i needed into the report file [as a table] at run time.

as i remember - was using the driver set for the HP LJ III - its a tad old, but combined with pcl5e it was quite stable over a network.

The other HP supplied drivers were a tad messy, either having memory leak problems or really not rendering pcl properly.

there was some discussion a while back about taking a report file, compiled into your app, and creating a copy of the frx/frt files externally [with some other name], finding the record you want, stuffing the code you need in the right place, then running the report based on the new report file name.

not sure if it was on the UT, VFUG, Profox, or where - but I took a piece of it way back then and made it work as well. But its been some time now - about 3 years ?

hth - mondo regards [Bill]