SPF Files - more questions

["David A. Beck" <david.beck@US.CGEYC.COM>]

Hi All,

I know that SPF had been discussed time and time again.  But I have yet
another question that I can't find the answer too.

I have written an SQR that uses multiple fonts and size formats.  It
produces an SPF file that I can send directly to the printer using the
-printer::wp flag at runtime, combined with using all the necessary
declare-printer and init commands.  I change the font within the SQR by
sending the font-init string directly to the printer also.  This all runs
great when I'm on the client.  Now that I'm running on the server, none if
it will work.  Here are my questions and the steps I've already tried:

1.  Change the init-string within the SQR?  I assume I have to use the
init-string that is particular to the printer attached to the server.
Also, I've had to change the individual font strings within the SQR.  Is
this correct?

2.  What flag do I use instead of -printer::wp?  I assume that I can't use
this flag since I'm not running through windows.

Any other advice on how to print a report with different fonts and font
sizes would be appreciated.  The errors we are currently getting are the
following:

1.  Sometime the report will print but the fonts are huge and in the wrong
places.
2.  Sometimes only garbage will print out of the report ( I think the
garbage is the SPF file content formatted for a different printer maybe)

We are using Oracle, PeopleSoft (not that this matters), and Unix.  All of
which are very recent versions.

Thanks very much for your help and time,

Dave



______________________________________________________________________
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
us immediately by responding to this email and then delete it from your
system. Cap Gemini Ernst & Young is neither liable for the proper and
complete transmission of the information contained in this communication
nor for any delay in its receipt.