Re: Print jobs get out of order between workstation and printer
From: Dan Freeman (spam_at_microsoft.com)
Date: 12/08/04
- Next message: Dan Freeman: "Re: MSDE Help"
- Previous message: Paul Pedersen: "Re: MSDE Help"
- In reply to: Ook: "Print jobs get out of order between workstation and printer"
- Next in thread: Ook: "Re: Print jobs get out of order between workstation and printer"
- Reply: Ook: "Re: Print jobs get out of order between workstation and printer"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 7 Dec 2004 16:28:58 -0800
My guess is you've just been lucky all along. <g>
The whole "zen" of printing in Windows is that your app "finishes" what it
needs to do and hands the whole shooting match off to Print Manager. What
happens there is none of your app's business and it's up to Print Manager to
sort out the details (including restarting after paper jams, etc.).
Your app no longer has to "talk to" the printer. You're always talking to
Windows. And that's all well and good, except when it isn't. <g>
I'm wondering what kind of response you might get in one of the Windows
newsgroups. I think there's even an MVP for printing, believe it or not. But
I don't know which groups he frequents.
There's probably some server-side setting that will tell print manager to
always pull printjobs from the queue in FIFO order. There *should* be
anyway.
Dan
Ook wrote:
> We have an app running on WinXP workstations, app is hosted on a
> Win2003 server. Printer is connected to theWin2003 server.
> Application does this:
>
> For lnCounter = 1 to 3
> report form <myreport> range 1,1 to printer noconsole
> Endfor
>
> For lnCounter = 2 to lnMaxPages
> report form <myreport> range lnCounter, lnCounter to printer
> noconsole Endfor
>
> The basic idea here is that each page prints three times: Page 1
> prints 3 times, page 2 prints 3 times, etc. Normally, we don't have
> any more then 2 pages to print, so it comes out on the printer as
> 1,1,1,2,2,2. (why wasn't this done in one loop? I didn't write the
> code...).
>
> Last night we rebuilt the app and deployed it to the server. The
> server hasn't changed, the report hasn't changed, the printer hasn't
> changed, the printer driver, the code that prints this report hasn't
> changed. The only thing that changed is that we rebuilt the app
> because of changes in areas unrelated to this particular report.
> Today, the report prints like this: 1,2,1,1,2,2. I examined the code,
> and don't see what would cause this. If I pause the print queue on
> the server while they print, and then unpause it after the app is
> done, it comes out in the proper order. If I print to a different
> server, it prints fine. My theory is that the app is printing in the
> proper order like it always has, and the server is somehow mixing up
> the order that they should print.
>
> The windows guys have no clue what to do about it. We have no clue
> why it started doing this just today, and why it does this on just
> this one server, let alone how to control it. I believe I can fix
> this in the app by putting a SET PRINTER TO after the printing of
> each page, and if necessary by putting a pause of a second or so
> between each page: 1,1,1, <set printer to><pause 2 seconds>2,2,2<set
> printer to><pause 2 seconds>.
>
> But it just worries me that after weeks and weeks of testing, it just
> now is starting to do this for no reason that we can discern.
- Next message: Dan Freeman: "Re: MSDE Help"
- Previous message: Paul Pedersen: "Re: MSDE Help"
- In reply to: Ook: "Print jobs get out of order between workstation and printer"
- Next in thread: Ook: "Re: Print jobs get out of order between workstation and printer"
- Reply: Ook: "Re: Print jobs get out of order between workstation and printer"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
