Thanks, Larry, I'm going to try projecting the data from the view to a table and running the report against the table. I can't think why it would make any difference but who knows.
I don't think there's much point in trying to overcome that sort of limit for the page number if that is the problem. In many ways it ought to be reduced to save trees!! Regards, Alastair. ----- Original Message ----- From: "Lawrence Lustig" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Thursday, February 24, 2005 6:37 PM Subject: [RBG7-L] - Re: Problem with reports (continued...) > > 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. > > 8-bit signed int being used for the page number? That may not be > overcome-able. > > > 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? > > Look for a similar problem -- maybe overruning a variable type in a SUM > variable, or something? > -- > Larry >
