Report must be on one 'screen-page'

We are producing a Matrix report that we want to have on one page. The width of the height is unpredictable.

This report is never printed, only used for browsing of export to excel.

How can we achieve this, w've tried to play with the sizes but this is still 'hardcoded', and setting height and with to 400 makes DevStudio crash, over and over.

Any suggestions ....

With suggestions we mean, on the 'one' page, not for the crash .....

If this is Reporting Services 2005, you can set the Report.InteractiveHeight property to 0 which means unlimited height in interactive renderers (HTML, preview).

-- Robert

|||Works perfect, thx.|||

Hi anyone,

my problem is a bit simillar with harry but we are making a report and when viewing it, we still see one page even how long the report is, I had viewed the XML code and search fot the property Report.InteractiveHeight but I fouond nothing.

Can anyone help me with this? thanks a lot... we need to cut the report in pages.....God Speed

Report layout:- Inconsistencies between page height and HTML Rendered

I'm having problems with what is displayed in the browser being different to what is defined in the RDL and what is exported to PDF.
I have set height to 21cm and width to 29.7 with 0cm margins. There is one table in the report.
When I export the report to PDF its fine, all pages are 21x29.7cm, landscape.
However, when I view the report in the report manager (in a browser) the pages are much longer than they should be... nearly twice as long (as if to make the report portrait again?)
Has anybody had this problem with lanscape reports? Any ideas on how to resolve this?
I've made lots of different landscape reports and get the problem every time. I find it hard to believe that no one else is having this issue...
ThanksI'm having this problem, too, but since the reports export to PDF no problem, i've considered it a low priority. I'm not even convinced it's a bug, as such, due to the nature of the web and the fact that web-delivered information generally runs on pages a great deal longer than standard portrait-sized pages. That is, I've chosen to consider the page-length property to be a PDF-specific property, and not even applicable to ASP-delivered reports. It doesn't bother me to have users browsing the reports online in this format as long as they can ultimately export them to PDF if they wish.

What does bother me is the seeming randomness of the length of the ASP-delivered report pages. Some of the pages seem double-lengthed, others triple or more. What gives?

|||I know what you, however, its my users that are complaining about it!
If there was some way of being able to "lock" the table headings it wouldnt be a problem - is there any way this can be done? It is one of the most requested features of my users.
Any help is much apprerciated.|||

In SQL Server 2005, you can 'lock' the headers for a table or a matrix.

If you right click the border of the table in the Layout pane of report designer, on the General tab in the Table Properties dialog, there is a check box called "Header should remain visible while scrolling". If you check that, in HTML the table header will always be shown.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||I had the same problem and solved it, so thought i would share this with anyone who comes across it. I don't know why it exactly occurs but if you change the Interactive page size to be a bit larger then the html is rendered as the pdf and the pdf is unaltered. Interactive page is is reached by clicking on the yellow right hand side of the report off the actual report and then in the properties pane.|||

my report is displayed as one long page when viewed in the browser, while it is displaying correctly in several pages when exported to PDF. Can you please helpe me!!

Regards

Dwarka (hdwarka@.yahoo.com)

Report layout:- Inconsistencies between page height and HTML Rendered

I'm having problems with what is displayed in the browser being different to what is defined in the RDL and what is exported to PDF.
I have set height to 21cm and width to 29.7 with 0cm margins. There is one table in the report.
When I export the report to PDF its fine, all pages are 21x29.7cm, landscape.
However, when I view the report in the report manager (in a browser) the pages are much longer than they should be... nearly twice as long (as if to make the report portrait again?)
Has anybody had this problem with lanscape reports? Any ideas on how to resolve this?
I've made lots of different landscape reports and get the problem every time. I find it hard to believe that no one else is having this issue...
Thanks
I'm having this problem, too, but since the reports export to PDF no problem, i've considered it a low priority. I'm not even convinced it's a bug, as such, due to the nature of the web and the fact that web-delivered information generally runs on pages a great deal longer than standard portrait-sized pages. That is, I've chosen to consider the page-length property to be a PDF-specific property, and not even applicable to ASP-delivered reports. It doesn't bother me to have users browsing the reports online in this format as long as they can ultimately export them to PDF if they wish.

What does bother me is the seeming randomness of the length of the ASP-delivered report pages. Some of the pages seem double-lengthed, others triple or more. What gives?|||I know what you, however, its my users that are complaining about it!
If there was some way of being able to "lock" the table headings it wouldnt be a problem - is there any way this can be done? It is one of the most requested features of my users.
Any help is much apprerciated.
|||

In SQL Server 2005, you can 'lock' the headers for a table or a matrix.

If you right click the border of the table in the Layout pane of report designer, on the General tab in the Table Properties dialog, there is a check box called "Header should remain visible while scrolling". If you check that, in HTML the table header will always be shown.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||I had the same problem and solved it, so thought i would share this with anyone who comes across it. I don't know why it exactly occurs but if you change the Interactive page size to be a bit larger then the html is rendered as the pdf and the pdf is unaltered. Interactive page is is reached by clicking on the yellow right hand side of the report off the actual report and then in the properties pane.|||

my report is displayed as one long page when viewed in the browser, while it is displaying correctly in several pages when exported to PDF. Can you please helpe me!!

Regards

Dwarka (hdwarka@.yahoo.com)

Report layout:- Inconsistencies between page height and HTML Rendered

I'm having problems with what is displayed in the browser being different to what is defined in the RDL and what is exported to PDF.
I have set height to 21cm and width to 29.7 with 0cm margins. There is one table in the report.
When I export the report to PDF its fine, all pages are 21x29.7cm, landscape.
However, when I view the report in the report manager (in a browser) the pages are much longer than they should be... nearly twice as long (as if to make the report portrait again?)
Has anybody had this problem with lanscape reports? Any ideas on how to resolve this?
I've made lots of different landscape reports and get the problem every time. I find it hard to believe that no one else is having this issue...
Thanks
I'm having this problem, too, but since the reports export to PDF no problem, i've considered it a low priority. I'm not even convinced it's a bug, as such, due to the nature of the web and the fact that web-delivered information generally runs on pages a great deal longer than standard portrait-sized pages. That is, I've chosen to consider the page-length property to be a PDF-specific property, and not even applicable to ASP-delivered reports. It doesn't bother me to have users browsing the reports online in this format as long as they can ultimately export them to PDF if they wish.

What does bother me is the seeming randomness of the length of the ASP-delivered report pages. Some of the pages seem double-lengthed, others triple or more. What gives?|||I know what you, however, its my users that are complaining about it!
If there was some way of being able to "lock" the table headings it wouldnt be a problem - is there any way this can be done? It is one of the most requested features of my users.
Any help is much apprerciated.
|||

In SQL Server 2005, you can 'lock' the headers for a table or a matrix.

If you right click the border of the table in the Layout pane of report designer, on the General tab in the Table Properties dialog, there is a check box called "Header should remain visible while scrolling". If you check that, in HTML the table header will always be shown.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||I had the same problem and solved it, so thought i would share this with anyone who comes across it. I don't know why it exactly occurs but if you change the Interactive page size to be a bit larger then the html is rendered as the pdf and the pdf is unaltered. Interactive page is is reached by clicking on the yellow right hand side of the report off the actual report and then in the properties pane.|||

my report is displayed as one long page when viewed in the browser, while it is displaying correctly in several pages when exported to PDF. Can you please helpe me!!

Regards

Dwarka (hdwarka@.yahoo.com)

Report layout:- Inconsistencies between page height and HTML Rendered

I'm having problems with what is displayed in the browser being different to what is defined in the RDL and what is exported to PDF.
I have set height to 21cm and width to 29.7 with 0cm margins. There is one table in the report.
When I export the report to PDF its fine, all pages are 21x29.7cm, landscape.
However, when I view the report in the report manager (in a browser) the pages are much longer than they should be... nearly twice as long (as if to make the report portrait again?)
Has anybody had this problem with lanscape reports? Any ideas on how to resolve this?
I've made lots of different landscape reports and get the problem every time. I find it hard to believe that no one else is having this issue...
ThanksI'm having this problem, too, but since the reports export to PDF no problem, i've considered it a low priority. I'm not even convinced it's a bug, as such, due to the nature of the web and the fact that web-delivered information generally runs on pages a great deal longer than standard portrait-sized pages. That is, I've chosen to consider the page-length property to be a PDF-specific property, and not even applicable to ASP-delivered reports. It doesn't bother me to have users browsing the reports online in this format as long as they can ultimately export them to PDF if they wish.

What does bother me is the seeming randomness of the length of the ASP-delivered report pages. Some of the pages seem double-lengthed, others triple or more. What gives?

|||I know what you, however, its my users that are complaining about it!
If there was some way of being able to "lock" the table headings it wouldnt be a problem - is there any way this can be done? It is one of the most requested features of my users.
Any help is much apprerciated.|||

In SQL Server 2005, you can 'lock' the headers for a table or a matrix.

If you right click the border of the table in the Layout pane of report designer, on the General tab in the Table Properties dialog, there is a check box called "Header should remain visible while scrolling". If you check that, in HTML the table header will always be shown.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||I had the same problem and solved it, so thought i would share this with anyone who comes across it. I don't know why it exactly occurs but if you change the Interactive page size to be a bit larger then the html is rendered as the pdf and the pdf is unaltered. Interactive page is is reached by clicking on the yellow right hand side of the report off the actual report and then in the properties pane.|||

my report is displayed as one long page when viewed in the browser, while it is displaying correctly in several pages when exported to PDF. Can you please helpe me!!

Regards

Dwarka (hdwarka@.yahoo.com)

Report Layout... TextBox Issue

I have two TextBoxes, they are next to each other and they touch.
According to their properties they are the same height, they are also the
same distance from the top.
Preview: they line up perfectly
After Deployment: one appears as though it is a slightly different height
Export To PDF: suddenly they're the same again
Why is this happening and how can I fix it?There are various properties on the text box you can set to specify where
it is located. If they have the same properties, that means they actually
want to be located in the same space. But the HTML viewer will position
them differently because it does not support overlay.
<Height></Height>
<Width></Width>
<Top></Top>
<Left></Left>
--
| Thread-Topic: Report Layout... TextBox Issue
| thread-index: AcS6nZhfn6F0qzGsTYehI9XjssWUhg==| X-WBNR-Posting-Host: 64.86.141.134
| From: "=?Utf-8?B?TUVSNzg=?=" <MER78@.discussions.microsoft.com>
| Subject: Report Layout... TextBox Issue
| Date: Mon, 25 Oct 2004 07:19:10 -0700
| Lines: 10
| Message-ID: <4592BB8A-993A-4A7A-98F1-2690E2E5658E@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.reportingsvcs:33048
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| I have two TextBoxes, they are next to each other and they touch.
|
| According to their properties they are the same height, they are also the
| same distance from the top.
|
| Preview: they line up perfectly
| After Deployment: one appears as though it is a slightly different height
| Export To PDF: suddenly they're the same again
|
| Why is this happening and how can I fix it?
||||I think I mis-worded my question... I've had endless problems with text boxes
that touch... at least according to their properties they don't overlap... it
looks ok in one format... in another boxes get pushed onto other lines etc...
especially in excel...
I've started using a table for text boxes that touch whenever I can...
though it took me awhile to notice that you can use a table without having it
connected to a data source... if you put all of your stuff in header rows.
""Brad Syputa - MS"" wrote:
> There are various properties on the text box you can set to specify where
> it is located. If they have the same properties, that means they actually
> want to be located in the same space. But the HTML viewer will position
> them differently because it does not support overlay.
> <Height></Height>
> <Width></Width>
> <Top></Top>
> <Left></Left>

Report Layout Width and Height for Landscape on Legal Paper??

I have a very large report that can't squeeze into Landscape on Letter size
paper. I was wondering if anyone knew the dimensions for Landscape on Legal
size paper. Is this possible?
Thanks in Advance.A4 21x29.7
Letter 21.5x27.9
Siew Fai|||Thanks.
"Siew Fai" <siewfai.hoy@.gmail.com> wrote in message
news:1118265794.339658.254270@.z14g2000cwz.googlegroups.com...
> A4 21x29.7
> Letter 21.5x27.9
> Siew Fai
>