Local Printing To PC or Thin Client - Final Resolution

[Dennis Malen]

Brian,

I never respond with a resolution unless it works. It is only after it is
tested that I share that info.

It works perfectly with one page or multi page reports. We are using this
for our managers who log into our system through the web. It's great!

We have also developed another approach which is to run the report through
processing i.e. using "system". This allows us to check the type of terminal
and to change the initiation and termination codes on the fly.

What you would do is to set up different executable files that have code
similar to the following:

echo "\033[5i"
cat $1
echo "\033[4i"

Then when you run the report drop it to a file using "printer file".

If the name of the executable was "tprint" and the name of the filepro file
is "test" you would execute the following:

tprint test

The foregoing will deliver the print job to the printer attached to the PC
or thin client that requested it. As I said it works perfectly. It is also a
lot faster than "printer local" or -PT etc.

Brian, if you prefer not to use it, don't.

I posted this for those that do want to take advantage of it in order to
solve a problem I have always experienced.

The choice is yours.

Best regards,

Dennis Malen
516.479.5912

----- Original Message ----- 
From: "Brian K. White" <brian at aljex.com>
To: "filePro mailing list" <filepro-list at seaslug.org>
Sent: Thursday, January 06, 2005 12:08 AM
Subject: Re: Local Printing To PC or Thin Client - Final Resolution


>
> ----- Original Message ----- 
> From: "Dennis Malen" <dmalen at malen.com>
> To: <filepro-list at lists.celestial.com>
> Sent: Wednesday, January 05, 2005 7:54 PM
> Subject: Local Printing To PC or Thin Client - Final Resolution
>
>
> I posted a problem today that has been resolved. As I normally do I
provide
> the resolution for everyone else's use.
>
> Problem: I needed to print to a local printer attached to either a PC or a
> Wyse Thin Client. I am on AIX Unix. When using -PT or Printer Local I had
> problems printing. Either the job did not print or the print job got hung
up
> and had to be forced (where it didn't look great.). The PN and PS codes
were
> in TERMCAP.
>
> Resolution: You have to create your own PN and PS codes in the document
> setup in Filepro with the following:
>
> Initialize Print Code: $1b [5i      (PN)
> Terminator Print Code: $1b [4i   (PS)
>
> Obviously, the foregoing codes must be placed in the printer definition
that
> you are using. You are creating your own PN and PS codes.
>
> This method is much faster than using -PT or Printer Local and much more
> efficient.
>
> Again, thanks to all those that responded.
>
> -----------
>
> Have you actually *tried* that?
>
> Generally, "the right way" is not the right way for years and years for no
> reason and you or I will think up something better in a day.
>
> If you run a report, and it uses the above print code table, then all the
> record-by record screen updating that fp does while the report is
> printing.... winds up in the prin job!
>
> You might not notice this with single page forms issued from clerk because
> the way clerk prints a form might _just happen_ to not send any data to
the
> screen while the form command is executing.  That doesn't save you from
> getting a "Do it right or at least please know what you are doing before
> suggesting others do it wrong" however.
>
> Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro BBx  Linux SCO  Prosper/FACTS AutoCAD  #callahans Satriani
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>