"Tom" wrote:

> I have the same problem when using nested lists - I'm assuming you are using
> lists and not tables. There is an implicit Keep Together on lists that force
> the whole list to the next page if it can't fit on the current page.
>
> I've raised a support incident for this behaviour and been told the product
> is working as designed. The solution, they say is to use tables and not
> lists. Unfortunately our reports designer product generates lists as the
> underlying rdl and not tables.
>
> It doesn't seem to matter to Microsoft that we have a multi-million $
> project with lots of potential new revenues for Microsoft -they still refuse
> to do anything about it and [provide us with a fix.
>
>
>
> "andrei" wrote:
>
> > Hi Group,
> >
> > This is a repost - original message posted on Dec.20th.
> >
> > We are using Win 2000, SQL RS 2000sp2 and SQLServer 2000(sp3) and we are
> > rendering to PDF.
> >
> > In most of our reports, in the body we have a title and a description,
> > followed by a table with a grouping structure like this:
> >
> > Title
> > GroupHeader1 (visible)
> > GroupHeader2 (visible)
> > GroupHeader3 (visible)
> > Details (invisible)
> > GroupFooter3 (visible)
> > - subreport sr3.a
> > - subreport sr3.b
> > GroupFooter2 (visible)
> > - subreport sr2.a
> > - subreport sr2.b
> > GroupFooter1 (visible)
> > - subreport sr1.a
> > - subreport sr1.b
> >
> >
> > Depending on the amount of data displayed in the subreports (3, 2, 1), the
> > generated PDF document has unexpected page breaks.
> > Sometimes, all the parts of the table fit on one page and they are indeed
> > displayed all on the first page - this is OK.
> >
> > Some other times, when the number of records to be displayed in subreports
> > is bigger, the PDF rendering engine decides to insert a page break before
> > the first subreport that would not fit entirely on the first page. When this
> > happens, the first page contains only the group headers, the rest of it is
> > left blank (which most of the times makes up to 75% of the page) and the
> > rest of the report goes on from the 2nd page.
> >
> > We had complaints from our customers, but we were not able to find a
> > solution to this behaviour...
> > I posted this question a few months ago (maybe in april/may of 2005) and the
> > opinions at that time were that the service packs will take care of this
> > thing.
> > We tried with SQLRS without any sp, then with sp1 and with sp2, but the
> > behaviour is the same...
> >
> > Could anyone please help with this issue ?
> >
> > Many thanks !
> >
> > PS - this is what our PDF reports look like:
> >
> > == page 1 ==
> > Title
> > GroupHeader1
> > GroupHeader2
> > GroupHeader3
> > //...empty page...//
> > ....
> > ....
> > ....
> > ....
> > ....
> > ....
> > == page 2 ==
> > GroupFooter3
> > - subreport sr3.a
> > - subreport sr3.b
> > GroupFooter2
> > ....
> > .... and so on.
> >
> >
> >