Re: Printing Issue

[Sayre John <John_Sayre@GAP.COM>]

I had that problem, too.  What it seemed like was that the SQR was running a
query that took a long time
to create a line to print.  In the meanwhile,  the printer had "timed out" on
the job and reverted to its default
print setup.

We modified the Standard Headings to print the printer init string every time a
header was printed, which
solved the problem except when there were network/DB problems which slowed
things too much.

I also saw a suggestion the instead of using printer = -HP, you use printer =
-WP, which forces it to print
as a windows formated report NOT AN LIS.  Its been 6 months since iI used PS, am
forgetting the file
type that SQR uses if  you don't print to LIS.   (Maybe .spf)

We did use -WP to print some of our highly formatted reports such as those with
BitMaps.  They go
directly to the printer and none of it prints until the entire report is done,
and the .spf file does not
remain on harddrive















John Milardovic <milardj@SX.COM> on 05/31/2000 10:18:49 AM

Please respond to sqr-users@list.iex.net



 To:      SQR-USERS@list.iex.net

 cc:      (bcc: John Sayre/SB/GAPINC)



 Subject: Re: Printing Issue






I recall that there was a discussion of this within the past year but I
can't recall the details or solution.  If no one else replies do a search of
the SQRUG archives.

John Milardovic


> -----Original Message-----
> From: John Ferguson [SMTP:jferguso@DOAS.STATE.GA.US]
> Sent: Wednesday, May 31, 2000 10:49 AM
> To:   SQR-USERS@list.iex.net
> Subject:      Printing Issue
>
> I have a report that I wrote for peoplesoft that prints fine when run on
> the server but occasionally does some weird things when run from the
> client.
>
> When run from the client, most of the time the report will print
> landscape, 180 chars. per line, just like it is supposed to. But sometimes
> it will start printing fine and then the printing converts to protrait and
> about 70 chars. per line.
>
> I can't seem to be able to find the cause. The place where the printing
> changes is never the same. The only thing that I can think of is that
> somehow the setting on the printer are getting reset when another job gets
> sent to the printer while the report is printing.
>
> Has anyone run into this problem? Does anyone know of a fix or work
> around?
>
> John