[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
Re: Printing Issue
We have to clarify the way, SQR manage a printer.
In fact SQR do not manage the printer.
What are the step cover by sqr :
1) Sqr execute your code
produce a spf file
2) Convert your spf file regarding the -printer option
produce a lis file
And at this step you send the lis file to the printer.
So you see that if you have printer issu using lis file, it come from
your spoolmanager or your network or your printer.
when you use the -printer:WP, sqr do not produce .lis file but sent
dirrectly the output (in windows format) to the windows spooler.
This option is more difficult to tune in an heavy system this have to be
configure this your windows spooler.
Some spool protocol over the network does not manage properly the end
of a job. It is difficult to determine when the file sent is finished.
Some determine the end of the file, by a parameter that say if nodata is
send until N second then the job is finish.
Hope this clarify the print subject and help you in your investigations.
These problem is more spooler/printer problem than sqr.
Franck,
Peter Clark wrote:
>
> We also experienced that type of problem. Seems that whenever there was a
>network (either WAN or LAN) delay, the printer would return to default
>settings (and when you are a large organization with a couple of hundred PS
>users in dozens of regional offices (some with a couple of dozen LANS within
>each) stretched over 6000 miles between the Pacific and the Atlantic, you do
>tend to experience network delays). PeopleSoft said it was a Brio problem,
>Brio said it was a Novell problem, Novell said it was an HP problem, HP said
>it was a PeopleSoft problem. Since it was always someone else's problem, we
>couldn't get anyone to address the issue.
>
> While PeopleSoft, Brio, HP and Novell were busier pointing fingers at each
>other than on addressing the issue, thanks to some assistance from members of
>this maillist we were able to resolve the issue by changing all our reports to
>generate HP SPF files (-printer:HP) instead of .LIS files and we haven't had a
>hint of a problem since.
>
> HTH,
> Peter
>
> >>> John Ferguson <jferguso@DOAS.STATE.GA.US> 2000/05/31 11:49:23 am >>>
> 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
begin: vcard
fn: Franck Masson
n: ;Franck Masson
org: Brio Technology EMEA
adr;dom: Le capitol;;55 av. des champs Pierreux;Nanterre;92000;;
email;internet: franck.masson@brio.com
title: Sales Manager Northern Europe
tel;work: 33 1 55 69 36 00
tel;fax: 33 1 47 25 02 59
tel;home: Mobile : 33 6 84 80 17 05
x-mozilla-cpt: ;0
x-mozilla-html: FALSE
version: 2.1
end: vcard