Sounds like the 'Spooler' and the way 7.5 was/is handling it. As I recall on 6.5++ there was a different way of handling printers and the way it was spooled. I would try printing to a file and if it fails then you have a problem. If it completes the print job, I would have to look at the way Windows is handling the print job. Also if networked this throws in a few more little things to check.
I am going to get corrected here but I will start anyways. "Print Job" , goes to local print buffer - then to the printer depending on if it says direct print or Spool. Then if it goes to the server it could then Spool in there and then go on its merry way to the printer. Good ---- but how much memory did I have? I then only take what I can and send a hold on any more. Perhaps I would try 'Direct Print' and then this locks this station up till the job is complete. By pass all memory options. What happens when you do a local print on a different machine to a different Printer!. I tend to lean towards the printer and its memory. I had problems back when memory was small and expensive and getting errors. Do an 'Admin Feature' from the printer and see how much it has. You might just be overloading the memory and need to print direct and let the local machine cache/spool that print job. If you did a print to file you have kind of an idea as to what size you are looking at. I have yet to have the issues that I used on any print job. Like I used too. I hated those old dos and pre- 7.6 days. I have some heavy graphics and jpg's going into my HP and 20 pages that have each those bmps and in the past it would have died. Not the same number but I bet the jpgs's are taking up a lot of room memory wise. I suppose another RBase user can better explain memory mapping along with the spooling of print jobs. So in short ' Try Print Direct' and see what happens and let us know. Or view the printer properties and let us know that first. It would help me better understand, certainly if it is in 'Print Direct' mode now. Control Panel>Printers and Faxs>ThatPrinter>Properties>Advanced> half way down the screen Sincerely, Paul Dewey Hope it help you out. From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, March 23, 2009 5:33 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Printing a whole buncha reports I think someone on this list had this problem recently, but I can't remember for sure. I think I responded about printing a hundred pages at a time... memory's short. A client prints monthly statements, thousands of them at once. She was in 6.5++ windows. We converted it to 7.5, with no changes to the statement. When printing (from the same workstation as always) we would get maybe a couple hundred and then it would stop with some message about "report being out of bounds" or something like that. So we kept 6.5 around and still do the statements from there. She wants me to do some changes to the statement and asked if I wanted to try an upgrade again, but doesn't want to go to 7.6 unless I can prove that it will print these statements. But neither of us wants to kill trees to "test" whether this will work in 7.6. Anyone doing this and having no problems at all getting thousands of reports to print? Or offer a reason why 7.6 might be doing something different so that this approach will not work? Karen
