dreport spools output to wrong printer

Kenneth Brody kenbrody at bestweb.net
Fri Jul 29 13:13:21 PDT 2005


Quoting Barry Wiseman (Fri, 29 Jul 2005 15:58:10 -0400):

> Spent this afternoon pounding my head over a report that filePro was
> stubbornly sending to the wrong printer.
[...]
> config file had (irrelevant entries omitted):
>
> printer7 = jeff,dr_hp3,lp -s -djeff,Jeff's printer
> printer8 = mary,dr_hp3,lp -s -dmary,Accting printer
> printer9 = dr_hp3,dr_hp3
>
> Output table had Printer name: dr_hp3
>
> With no -p on the command line, no value in LPDEST, no "printer"
> statements in processing, I would expect the report to go to the default
> printer, "hp8100".  Instead, it was going to "jeff".

The output format had the printer name "dr_hp3".  Therefore, since
printer7 is of type "dr_hp3", it went there.  (That is, "jeff".)

Why would you expect filePro to go to the default printer, when the
output format specifies "dr_hp3"?

This is the expected, documented behavior.

> After much head-scratching, I edited the config table to read:
>
> printer7 = dr_hp3,dr_hp3
> printer8 = jeff,dr_hp3,lp -s -djeff,Jeff's printer
> printer9 = mary,dr_hp3,lp -s -dmary,Accting printer
>
> whereupon the job went to the default printer as expected.

It's still picking printer7 (the first "dr_hp3").  However, since
this has no destination specified, it uses the default.

> So fP was was grabbing the first definition for the printer *type*
> dr_hp3, not the one for printer *name* dr_hp3.
>
> Bug or feature?

Perhaps I'm missing something.  How, exactly, did you specify "dr_hp3"?

--
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com


More information about the Filepro-list mailing list