PRINTER type and PRINTER name

Nancy Palmquist nlpalmquist at comcast.net
Wed Mar 31 08:06:53 PDT 2010


I am posting this because it needs to be documented for others.

I have a project where we print forms from clerk on a Windows Computer.

I start by having them select a printer from a database list of 
printers.  That gives me the filepro
printer name.

I wanted them to use a different print code table than the one assigned 
to the printer they selected for the forms
that they print from this database.

So here is what I did.  In the @once processing, they select the 
printer, I issue the following commands:

printer type (my_prttype{"")
printer name (my_prtname{"")

We were getting the wrong print codes.  Not the ones I issued in the 
PRINTER TYPE command, but the table associated with the printer name. It 
is easy to tell you this now but it took a bunch of paper and testing to 
narrow down what was going wrong.  Our projects started trying to print 
to an envelop bin in a funny font.

Well my solution was simple, reverse the commands so it assigns the 
PRINTER TYPE after the PRINTER NAME.

For good measure, I added PRINTER TYPE before I process the various 
forms just to make sure it always uses the right table.

I also want to note in this posting that we tried to use FORMM to 
collect the various pages into one document.  The output always is 
followed by the same form so it would get the FORM command.  After a few 
records, we would get a memory error on the FORMM line of the 
processing.  Changing FORMM to FORM fixed that issue.  I tried 
everything to keep the FORMM so the pages would print in order properly, 
but to no avail.  We do not change printers or code tables after we pass 
the @once processing, so we were not telling it bad stuff.

I can not figure what it could be, except a bug.  I removed the 
initialization and termination codes on each form, because I thought 
maybe that was it, but inserting codes in a document should not crash 
memory.

Well these are my observations for today, hope you enjoy them. The list 
needed something filePro related.

Nancy



-- 
Nancy Palmquist



More information about the Filepro-list mailing list