printer file "name" - problem RESOLVED!!!!!

[Kenneth Brody]

Quoting Dennis Malen (Mon, 21 Mar 2005 13:59:05 -0500):

> Ken,
>
> Thanks for that piece of info concerning the fact that the nocodes
> printer does not have to be defined. I'll test it to see if it works
> without that definition.

The PRINTER TYPE command only uses the printer type.  It does not need,
nor does it use, any printer names defined to filePro.  (That's what
the PRINTER NAME command would be used for.)

> There are a number of people on the list that indicated it had to be
> defined. I remember that when I did not define the destination file in
> the printer definition in the printer config that it did not work. That
> is when I was told that I must have it defined and it did work. I even
> went out of my way to thank that person for the info.

You may be confusing multiple things here.  A printer definition assigns
a name to a type/destination combination.  If you defined a printer name
without giving it a definition, and then tried to use that printer by
name (such as the printer name which can be stored in an output format),
then I believe the default destination will be used for that printer.
However, since you were overriding both the type name destination in your
processing with the PRINTER TYPE and PRINTER FILE commands, that would
have no effect on the specific issue at hand.

[...]
> As far as your request that I let you know why my processing didn't work
> as it appears to be the same, I don't have an answer. I changed the
> processing so many times after I received a response from the list that
> I lost track.

I used the processing in your original post, as well as the processing in
your "RESOLVED!!!!!" post, and both were identical.  If you made any
changes along the way, you ended up with the exact processing that you
started with.

[..]

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