printer file "name" - problem

[Dennis Malen]

That's the entire processing.

----- Original Message ----- 
From: "Laura Brody" <laura at hvcomputer.com>
To: "Dennis Malen" <dmalen at malen.com>; "filePro mailing list" 
<filepro-list at seaslug.org>
Sent: Thursday, March 17, 2005 5:02 PM
Subject: Re: printer file "name" - problem


> On Thu, 17 Mar 2005 16:09:26 -0500, Dennis Malen <dmalen at malen.com> wrote:
>
>> Laura,
>>
>> I do have your Quick Reference Guide and also find it a handy reference.
>>
>> Your explanation of umask was great. I finally understand it, although I 
>> don't think I need it in my processing (unless you insist) as the file is 
>> being written to the /tmp file, although not correctly without 
>> modifications that I should not have to make (explained below).
>>
>> In conclusion, I think you are saying my processing code is correct.
>>
>
> The processing that you posted is correct, but could you post
> the entire prc table?
>
>> I will go back and try it again but the two problems I was initially 
>> having with this code are:
>>
>> 1. It would not over ride the defined printer in the report format. I 
>> solved that by copying over the report and not defining a printer 
>> (shouldn't have to do that);
>
> You can override it with either a PRINTER command in processing
> or one of the -P flags on the command line. If the PRINTER command
> isn't changing the printer destination, you must not be executing
> the PRINTER command in your processing table. Please post the code
> so we can point out any problems in it.
>
> As a test, add a printer definition to print to a file in
> Printer Maint, and then put a -PQ on your command line. Select the
> new printer and see what happens. It should override the printer
> definition in the output format just fine.
>
>>
>> 2. When I copied the report over so there was no interference with any 
>> defined printer (since there was none) the file created was composed of 
>> each record being written and then adding 63 blank lines (definition of 
>> the page length was 64) and wrote the next page in a similar fashion. 
>> Pulling 93 records creating 93 pages scrolling through the screen. When I 
>> defined the length of the page as 1 (as opposed to 64), it then printed 
>> correctly on the screen.
>
> It sounds like filePro was doing what you told it... the only
> question is, what do you want it to do? <g> Can I safely assume that
> you want the final report to have more than one record per page?
>
>
>> So I am really back to square one from my initial post.
>
> Please add the MSGBOX command on the line above the
> PRINTER command like Ken already asked you to do. Just
> humor us and verify that the PRINTER command is actually
> being executed.
>
> -- 
> Laura Brody, Publisher of the filePro Developer's Journal
> +------------- Hudson Valley Computer Associates, Inc ----------+
> | PO Box 859 120 Sixth Street    http://www.hvcomputer.com      |
> | Verplanck, NY 10596-0859       Voice mail: (914) 739-5004     |
> +------ PC repair locally, filePro programming globally --------+
>
>
>
>