Printer file - revisited

Dennis Malen dmalen at malen.com
Wed Mar 30 09:48:03 PST 2005


Jose,

It is within the processing because we offer 4 options as to how the report 
is to print. They can print hard copy, write to the file to save, excel 
format, and lastly e-mail the report.

We are a UNIX shop.

Dennis
----- Original Message ----- 
From: "Lerebours, Jose" <Jose.Lerebours at EagleGL.com>
To: "Fplist (E-mail)" <filepro-list at lists.celestial.com>
Sent: Wednesday, March 30, 2005 6:38 AM
Subject: RE: Printer file - revisited


Denis posted:

>
> If I have printer type "nocodes" somewhere in the processing
> table must I
> conditionally bypass that statement and just use "printer
> file" without
> using the additional "printer type" that you suggested (I
> assume that's the
> case in order to get print codes back into the file). The
> other way is to
> take advantage of the parameters of the printer that is
> defined in the
> report format or must I redefine a printer type so that the
> print codes are
> embedded in the file to be saved on the disk.
>
> In any event, you suggested that the printer type be defined
> after the
> printer file. Should that be reversed.
>

If you have command "printer type" within your code and you
do not want to execute it for all instances of your report,
then by all means, do make it a conditional statement.

I hope you are setting your printer target and type only once
and not every time you run through a record.

Why set this up within the printing process instead of within
the command line?

Are you a *nix or windows base shop?

Regards;


Jose Lerebours
_______________________________________________
Filepro-list mailing list
Filepro-list at lists.celestial.com
http://mailman.celestial.com/mailman/listinfo/filepro-list






More information about the Filepro-list mailing list