|
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.
|
- [RBG7-L] - Re: Problem with reports (continued...) Alastair Burr
- [RBG7-L] - Re: Problem with reports (continued...) Lawrence Lustig
- [RBG7-L] - Re: Problem with reports (continued...... Alastair Burr
- [RBG7-L] - Re: Problem with reports (continue... Alastair Burr
- [RBG7-L] - Re: Problem with reports (continued...) Javier Valencia
- [RBG7-L] - Re: Problem with reports (continued...... Lawrence Lustig
- [RBG7-L] - Re: Problem with reports (continued...... Emmitt Dove
- [RBG7-L] - Re: Problem with reports (continued...... Alastair Burr
- [RBG7-L] - Re: Problem with reports (continued...) Javier Valencia
- [RBG7-L] - Re: Problem with reports (continued...) Emmitt Dove
