[RBG7-L] - Re: Problem with reports (continued...)

[Javier Valencia]

Alastair: Just curious…why in the world would you want to generate a report with 32,000+ pages??? Would you ever print it? With a standard box of papers (in the States) having 10 reams (500 pages each), it would take six and one half cases, wow… I imagine it would also take a looooong time to open the stored file…and to print it… Javier,   Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66062-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 ================================================ Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all system and destroy all copies. ======================================================   -----Original Message----- From: rbg7-l@rbase.com [mailto:[EMAIL PROTECTED]On Behalf Of Alastair Burr Sent: Thursday, February 24, 2005 12:30 PM To: RBG7-L Mailing List Subject: [RBG7-L] - Re: Problem with reports (continued...)   A little bit more on this:   I have solved one of the problem reports but still cannot find out what is causing the problem with the other.   The solution is easy: it seems that there is a point at which the page number fails. Printing to the screen (thanks, Larry) showed me that the report "stopped" at page 32,693. Reducing the number of page breaks solved the problem.   Jumping to conclusions it would appear that 32k is the maximum for the page number. It has to be said that printing that number of pages to a printer is hardly likely!   The other report shows a very similar problem but does not respond to the same correction - at least, so far. In this case there are 18,803 records in the view with the appropriate where clause. I can browse this view and sort it with no problem (as expected). The report, however, stops at around record 12,800 on page 5158 yet when I break the report into two "halves" there is no problem. This is consistant both on screen and to a file - so I tend to exclude any file problems.   Has anybody got any further ideas that I might try? Regards, Alastair.