Printer file - revisited

[Dennis Malen]

Ken, thanks again.

The message you responded to was wriiten before I read your prior response. 
I get it now. It is very logical and now I'm able to do many more things 
that I wanted to do, especially creating a PCL document on the fly as one of 
my menu options in a report.

Dennis

----- Original Message ----- 
From: "Kenneth Brody" <kenbrody at bestweb.net>
To: "Dennis Malen" <dmalen at malen.com>
Cc: "Fplist (E-mail)" <filepro-list at lists.celestial.com>
Sent: Tuesday, March 29, 2005 7:33 PM
Subject: Re: Printer file - revisited


> Quoting Dennis Malen (Tue, 29 Mar 2005 18:53:04 -0500):
> [...]
>> 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.
> [...]
>
> Once again, PRINTER FILE has zero effect on which print codes are being
> used.  It was your PRINTER TYPE "nocodes" which caused the output to not
> have ny print codes.  (And it was the execution of the PRINTER TYPE
> statement, not merely its existence, that did it.)
>
> You don't have to do anything regarding your PRINTER TYPE "nocodes", but
> you have to remember that if you execute it, filePro will do as you tell
> it and not use any print codes.
>
> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
> http://www.hvcomputer.com
> http://www.fileProPlus.com
>
>
>