I have not had any problems printing large reports (500-2000 pages) form Rbase for Windows 6.5++ under Windows 98 or 98SE and most definitely not under RBase for DOS 4.5++. Is there a particular reason why you are printing individual reports and not one big report with page breaks between users/account/etc.? The only problem that I have encountered is that if the reports are short and run very fast, it sends a large number of (temporary) file names to the spooler and it runs out of space to store the file names (???), which would indicate that is not the size of the files but the sheer number, hence printing one large report may help with this issue. The only other thing that I can think is that since you are printing individual reports, they are likely being generated from within a loop in your program, you can try programming a delay (couple of minutes) every 100 reports or so, to allow the spooler to catch up.
Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln., Suite #14 Olathe, KS 66062-4571 (913)829-0888 (913)649-2904 FAX -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Goldberg Sent: Friday, October 11, 2002 9:40 AM To: [EMAIL PROTECTED] Subject: RE: Printing to high speed laser, revisited I have had problems in the past with the spooler in Windows 98. I usually turn off the spooler and send the print job directly to the printer. It helps. If possible I would recommend to upgrade the Win 98 machines to Win2k pro or XP pro. You will have a lot less problems with all the programs!! Dan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of tellef Sent: Friday, October 11, 2002 6:56 AM To: All Subject: Printing to high speed laser, revisited 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/ ================================================ 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/
