I have an app that prints thousands of statements a month, and the program hasn't changed much since 6.5 days. Each statement is calculated one at a time and printed one at a time. Most of the time the computer will lock up during the printing, which I assume is because RBase is printing so fast to the spooler, and the network/spooler/printer simply cannot keep up with the number of files waiting to print, and at some point RBase can no longer send jobs to the print queue. Luckily I've programmed it so that the user can come back in and easily continue where it left off, but it's a pain to have to do that. We've tried building in "waits" after so many statements print, but the program ended up taking like 6 hrs to run!
And yes, believe it or not, they are mailing the statements to their customers and have no wish to email them. So I'm thinking of utilizing PDFs instead, and I have the choice of generating 1000s of individual PDFs (where the user can then highlight multiple PDFs, right-click, "print" at their own schedule), or generating one huge multi-1000s page PDF. I have never created that big of a PDF. Is there a reasonable limit to the #pages RBase can print to a PDF file? Can someone tell me the largest PDF file they've ever generated? Thanks! Or if you have other suggestions..... Karen -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
