At times, I have run into problems (not necessarily with Rbase) trying to print individual print jobs. It seems that the spooler gets overwhelmed not by the size of the print jobs but by the sheer number of them, I do not know if there is a Windows limit. On the other hand I have had no problem generating Rbase reports that are several thousand pages long. I would suggest that you run the calculations first and save them in a table or view and then generate a report; you can easily break you report so each customer is printed on a separate page. Also, most printer drivers have the option of downloading the entire job to the printer or gradually spooling it to the printer; for this application, the second option might work better unless your printer has a lot of memory installed.
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 tellef Sent: Sunday, June 30, 2002 11:45 AM To: All Subject: Printing big jobs to high speed Hello all! A client is printing 1600 monthly statements to their customers. They bought a 12ppm Okidata to do the printing. In the RBWin program I wrote, it cursors through and is printing one customer at a time. The original thinking was that I have to do some calculations as each client is looked at, accumulating several variables depending on the customer's situation that are written to a file after all the printing is done. Running on Win98 workstations on a Win2K network, it seems the print spooler can't keep up. The cursor is very fast and after printing about 400 statements we start getting Spool32 errors. The client knows how to modify my program to have it start printing at wherever it left off, and she'll get maybe 300 more, then less and less. The hardware guy says the driver is right, installed brand new when the printer was brought in. She bumped up the printer memory to the max. I told her I could put a 'pause for <xxxx>' every 300 statements or so to see if that helps if we could determine how long to wait for it. My other thought -- if the spooler/printer can't handle 1600 individual print jobs, would it be able to handle a 1600-page single job better? I could change the the program to do all my calculations first, then have the report just break on the CustID. Printing to a file is not an option because we need to retain formatting. 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/
