Report always end with blank page

Hi,
Regardless of the set of data, I am finding that the report always ends with
a blank page.
I have tried several combinations of changing the KeepTogether parameter and
have made sure the PageBreakAtStart = false and PageBreakAtEnd = false
everywhere.
What could cause this extra page?
KevinThis has happened to me when my report contained an object, like a
table, that was a hair wider than the margins. Make sure your objects
are within the left and right margins.
Just an idea.
Shane
Kevin VanRiper wrote:
> Hi,
> Regardless of the set of data, I am finding that the report always ends with
> a blank page.
> I have tried several combinations of changing the KeepTogether parameter and
> have made sure the PageBreakAtStart = false and PageBreakAtEnd = false
> everywhere.
> What could cause this extra page?
> Kevin|||I also frequently get stumped by how non-obvious it is that report
items that are too wide are creating extra pages.|||there is nothing obvious about this topic really. I have followed all the
suggested fixes to the letter many times and still end up with blank page at
the end with a header. If there is a report item that is "too wide" ... it
is anything BUT obvious when I am certain that my page width < rt.margin +
body + lt. margin (from report page properties). If you have another
suggestion to add I am open to anything. I use them all. Thanks.
"Eva Pierce Monsen" wrote:
> I also frequently get stumped by how non-obvious it is that report
> items that are too wide are creating extra pages.
>|||I have reviewed each line of the actual XML of the RDL and confirmed that
margins + body do not exceed size of the page.
"MJT" <MJT@.discussions.microsoft.com> wrote in message
news:63C7514E-0AB3-478F-B955-E6456C7E486E@.microsoft.com...
> there is nothing obvious about this topic really. I have followed all the
> suggested fixes to the letter many times and still end up with blank page
> at
> the end with a header. If there is a report item that is "too wide" ...
> it
> is anything BUT obvious when I am certain that my page width < rt.margin +
> body + lt. margin (from report page properties). If you have another
> suggestion to add I am open to anything. I use them all. Thanks.
> "Eva Pierce Monsen" wrote:
>> I also frequently get stumped by how non-obvious it is that report
>> items that are too wide are creating extra pages.
>>|||Try ensuring that everything is smaller than the width of the page -
and check for anything that might be 'pushed down', in terms of height.
It is all too easy to get something just a hair off - and I find that
sometimes going to the exact limit (mathematically) means that you go
too far when you actually render|||In my table footer there is a cell with content that can be multiple lines
(includes CRLF within the data). Will this cause the issue? If so, what is
the fix for this knowing that I need the data to include these CRLF?
"Parker" <psmith@.iquest.net> wrote in message
news:1150977864.447449.124050@.y41g2000cwy.googlegroups.com...
> Try ensuring that everything is smaller than the width of the page -
> and check for anything that might be 'pushed down', in terms of height.
> It is all too easy to get something just a hair off - and I find that
> sometimes going to the exact limit (mathematically) means that you go
> too far when you actually render
>|||Kevin,
Yes, that's exactly something that could cause the extra page. Make
sure that your footer area is large enough to fully contain the largest
data including the CRLFs. Double check all the size and location
properties for page Header, Body and Page Footer to ensure everything
fits inside your report size. I always leave at least an eighth inch
leeway all the way around just in case.
Good reporting!!
toolman
Kevin VanRiper wrote:
> In my table footer there is a cell with content that can be multiple lines
> (includes CRLF within the data). Will this cause the issue? If so, what is
> the fix for this knowing that I need the data to include these CRLF?
> "Parker" <psmith@.iquest.net> wrote in message
> news:1150977864.447449.124050@.y41g2000cwy.googlegroups.com...
> > Try ensuring that everything is smaller than the width of the page -
> > and check for anything that might be 'pushed down', in terms of height.
> >
> > It is all too easy to get something just a hair off - and I find that
> > sometimes going to the exact limit (mathematically) means that you go
> > too far when you actually render
> >|||I believe this is a bug not a developer issue. We don't have this issue
with other reporting tools.
It is impossible to know during development the exact length of dynamic,
variable length data that is coming from a varchar(max) field. That is the
whole reason one looks to using a reporting tool like SQL Reporting
Services.
Is there anyone from Microsoft that can respond with a reasonable fix to
this bug?
"toolman" <timd@.infocision.com> wrote in message
news:1151065588.315448.204240@.c74g2000cwc.googlegroups.com...
> Kevin,
> Yes, that's exactly something that could cause the extra page. Make
> sure that your footer area is large enough to fully contain the largest
> data including the CRLFs. Double check all the size and location
> properties for page Header, Body and Page Footer to ensure everything
> fits inside your report size. I always leave at least an eighth inch
> leeway all the way around just in case.
> Good reporting!!
> toolman
> Kevin VanRiper wrote:
>> In my table footer there is a cell with content that can be multiple
>> lines
>> (includes CRLF within the data). Will this cause the issue? If so, what
>> is
>> the fix for this knowing that I need the data to include these CRLF?
>> "Parker" <psmith@.iquest.net> wrote in message
>> news:1150977864.447449.124050@.y41g2000cwy.googlegroups.com...
>> > Try ensuring that everything is smaller than the width of the page -
>> > and check for anything that might be 'pushed down', in terms of height.
>> >
>> > It is all too easy to get something just a hair off - and I find that
>> > sometimes going to the exact limit (mathematically) means that you go
>> > too far when you actually render
>> >
>|||Try adding border lines to all objects that don't have them, just to see if
there are any objects that behaves strangelly.
I've found that if you pub a matrix in a rectangle, and there's extra space
in that rectangle, the matrix will make sure that the rectangle ends the
same number of pixels to the right when the matrix is filled with columns -
which gives me a blank page, even if the rectangle is within the limits of
the margins.
Kaisa M. Lindahl Lervik
"MJT" <MJT@.discussions.microsoft.com> wrote in message
news:63C7514E-0AB3-478F-B955-E6456C7E486E@.microsoft.com...
> there is nothing obvious about this topic really. I have followed all the
> suggested fixes to the letter many times and still end up with blank page
> at
> the end with a header. If there is a report item that is "too wide" ...
> it
> is anything BUT obvious when I am certain that my page width < rt.margin +
> body + lt. margin (from report page properties). If you have another
> suggestion to add I am open to anything. I use them all. Thanks.
> "Eva Pierce Monsen" wrote:
>> I also frequently get stumped by how non-obvious it is that report
>> items that are too wide are creating extra pages.
>>