Karen, In 2.11 I came across a circumstance where my app was overwhelming the windows printer queue by virtue of sheer numbers of jobs. But my foggy recollection wants to believe it was Win 3.1... the limit seemed to have been about 100 jobs. What's funny is that I had a request to limit the number of invoices printed at once because of printer jams, out of paper ... (you know, 500 invoices completed in the tray and 500 in the queue and paper everywhere <g>) so now the app asks you to hit a key to continue with the next 50 and the other problem became moot.
I'd suggest the pausing routine as a trouble shooting method, if not a solution. Have you watched the queue as the printing is going on? Do the print jobs flush to the printer very quickly? If nothing has changed other than the printer, maybe it's the printer that can't handle all those separate jobs and more memory is a _liability_. If you watch the queue before and after the pause in printing is added (assuming things get better) you may come up with some alternate ideas (like pausing the windows printer queue...). Ben > Ben: > > >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 had suggested this to her but she didn't want to do it. I assume > that it wouldn't slow the actual printing down because even with a > couple second pause between jobs the program would still probably be > faster than the output from the printer. The problem she had was that > adding even a 3 second pause between 2000 print jobs would mean an > extra 1 hr 40 min before the computer would free up to do other jobs. > As it is now, the RBase program zips through all the print jobs and > then is immediately freed up. I also suggested a longer pause between > say every 50 jobs. We haven't tried this and maybe that's a better > option. Again she wouldn't go for it if the computer doesn't free up. ================================================ 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/
