Karen, I don't recall if I suggested this before, but if you're printing in a loop, try placing a pause just after the print statement... for a 12ppm printer I'd start with pause 5 and maybe shorten from there.
I haven't done this since 2.11(so I don't know if it can be done in RBW), but in addition, you could send a reset command to the printer in the footer of each report. Define the reset as a variable, and place the var on the report footer, making it wide enough to accommodate all the characters involved. If this isn't doable, you may be able to define the var separate from the form and "write" it to the printer immediately before or after the print command. Ben Petersen On 11 Oct 2002, at 9:56, tellef wrote: > > I asked for opinions about this before, and we tried all > solutions. None of the solutions helped, but getting a > replacement printer changed things a bit. > > PROBLEM: Printing monthly statements, one statement at > a time, anywhere from 200 - 2000 individual print jobs, > from RBWin, W2K network, Win98 workstations. They were > printing to an old, old HP laserjet and it came out > perfectly, no problems, but took about 4 hours! > > They bought a higher speed OKIData laserjet, put memory > in it to the max, and had all kinds of error messages pop > up, never could get an entire run to go even if only 200 > print jobs. RBase completed the job with no errors and > returned back to the menu. I originally suspected a > spooling problem, but since it spools perfectly to a much > slower printer (which means more jobs would be in the > spooler because they are being released more slowly) > I can't see how it could be the spooler. > > PARTIAL SOLUTION: Thinking the printer itself could be > defective they arranged for a replacement. They are using > the stock memory (don't know what it is) and didn't put > in extra. Printed a run and thought they got everything. > Hurrah! But at the end a page printed out with this error > message and they discovered that they were short 2 pages. > Any clue where this error message comes from? Printer? > Spooler? The message comes on separate lines, with this > alignment: > > /buffer 256 string def > statusdict begin > (@PJL TBNAME=) print > buffer printername pri > (may be going off the page > at this point) > > > Karen > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In > the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
