I have report that generates a person's resume. The resume sections
(experience, education, skills ...) do not page correctly when exported to
PDF or TIFF. Instead of keeping sections together on the same page the
sections is moved to the next page even though there is sufficient space left
at the bottom of the current page.
I would really appreciate any help since this is due next week.Hi Adil,
Did you solve this issue?.
I'm also got stuck with the same problem.
Please help if you have solved this issue.
Thanks,
Ranjith
"Adil" wrote:
> I have report that generates a person's resume. The resume sections
> (experience, education, skills ...) do not page correctly when exported to
> PDF or TIFF. Instead of keeping sections together on the same page the
> sections is moved to the next page even though there is sufficient space left
> at the bottom of the current page.
> I would really appreciate any help since this is due next week.
>|||No solution yet. I was hoping someone from Microsoft could look at this...|||I have the same problem.
Data groups are being put on new pages instead of flowing. "KeepTogether"
property for all data regions is set to "False" but the groups are still
moved to new pages.
In design preview mode the data layout is perfect - until I print preview
or export to pdf - extra pages get added.
I installed SP2 and that solved another problem that I had - the first page
was blank in print preview mode but this problem still persists.
Anyway - sorry I can't help you on this one but I am hoping MS knows that
more than one person is having this problem.
Cheers
"Adil" <Adil@.discussions.microsoft.com> wrote in message
news:8919C1C9-7E48-4A0D-A24A-D8CADD772DFE@.microsoft.com...
> No solution yet. I was hoping someone from Microsoft could look at this...|||Hi,
I got to know that, this behaviour is as per the design. When we have list,
they implicitly set Keep together property to true during the rendering time.
The workaround given by microsoft is to use "Tables" instead of "list" in
the reports.
I believe microsoft people will help us for sure to fix this issue,else we
have no other option to redesign the reports from the scratch using tables
instead of list.
Thanks,
Ranjith
"Tim Powers" wrote:
> I have the same problem.
> Data groups are being put on new pages instead of flowing. "KeepTogether"
> property for all data regions is set to "False" but the groups are still
> moved to new pages.
> In design preview mode the data layout is perfect - until I print preview
> or export to pdf - extra pages get added.
> I installed SP2 and that solved another problem that I had - the first page
> was blank in print preview mode but this problem still persists.
> Anyway - sorry I can't help you on this one but I am hoping MS knows that
> more than one person is having this problem.
> Cheers
>
>
> "Adil" <Adil@.discussions.microsoft.com> wrote in message
> news:8919C1C9-7E48-4A0D-A24A-D8CADD772DFE@.microsoft.com...
> > No solution yet. I was hoping someone from Microsoft could look at this...
>
>|||Thanks - tables work!
I originally used the wizard and to create a group -- the wizard uses lists,
not tables.
Anyway this issue caused me 2 days of work - I couldn't find any
information to solve this problem.
Thanks for the tip!
"Ranjith Prakash" <RanjithPrakash@.discussions.microsoft.com> wrote in
message news:89D8F795-E366-4B74-BB96-BEDC4370809A@.microsoft.com...
> Hi,
> I got to know that, this behaviour is as per the design. When we have
list,
> they implicitly set Keep together property to true during the rendering
time.
> The workaround given by microsoft is to use "Tables" instead of "list" in
> the reports.
> I believe microsoft people will help us for sure to fix this issue,else we
> have no other option to redesign the reports from the scratch using tables
> instead of list.
> Thanks,
> Ranjith
> "Tim Powers" wrote:
> > I have the same problem.
> >
> > Data groups are being put on new pages instead of flowing.
"KeepTogether"
> > property for all data regions is set to "False" but the groups are still
> > moved to new pages.
> >
> > In design preview mode the data layout is perfect - until I print
preview
> > or export to pdf - extra pages get added.
> >
> > I installed SP2 and that solved another problem that I had - the first
page
> > was blank in print preview mode but this problem still persists.
> >
> > Anyway - sorry I can't help you on this one but I am hoping MS knows
that
> > more than one person is having this problem.
> >
> > Cheers
> >
> >
> >
> >
> > "Adil" <Adil@.discussions.microsoft.com> wrote in message
> > news:8919C1C9-7E48-4A0D-A24A-D8CADD772DFE@.microsoft.com...
> > > No solution yet. I was hoping someone from Microsoft could look at
this...
> >
> >
> >
Showing posts with label pdf. Show all posts
Showing posts with label pdf. Show all posts
Monday, March 12, 2012
Friday, March 9, 2012
Pagination Issue when Rending to PDF
I am having a pagination issue with a report when I render to PDF. The
report is a patient form that is based on a single record that is returned
from a stored procedure. Most of the records are output fine, but some
records are not paginating properly and leave 3/4 page of blank space. The
field that follows on the next page is short and should definitely fit on
that page. The report renders fine in HTML, but the requirement is a PDF
format.
The body of the report is contained in a table. Each field of the report is
contained in its own row. If the field is blank, the entire row is hidden so
that only populated data is output in the report.
In troubleshooting this, I have removed the logic that hides the rows, but
the pagination is still not correct.
I have also made sure that the data is clean and doesn't have whitespace.
Any suggestions as to how to fix this problem?
TIAOn Dec 18, 8:47 pm, JC <J...@.discussions.microsoft.com> wrote:
> I am having a pagination issue with a report when I render to PDF. The
> report is a patient form that is based on a single record that is returned
> from a stored procedure. Most of the records are output fine, but some
> records are not paginating properly and leave 3/4 page of blank space. The
> field that follows on the next page is short and should definitely fit on
> that page. The report renders fine in HTML, but the requirement is a PDF
> format.
> The body of the report is contained in a table. Each field of the report is
> contained in its own row. If the field is blank, the entire row is hidden so
> that only populated data is output in the report.
> In troubleshooting this, I have removed the logic that hides the rows, but
> the pagination is still not correct.
> I have also made sure that the data is clean and doesn't have whitespace.
> Any suggestions as to how to fix this problem?
> TIA
You will want to check the width of the report. Normally, if it is
wider than 6.5" in design view, it will wrap once exported to PDF.
Also, if you are using a table control, you will want to put it into a
rectangle control, this should shrink the extra space. Hope this
helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Thanks for the quick reply. The report is slightly wider than 6.5" in design
mode to incorporate the header (which renders fine). The fields before and
after the blank space are very short (like 1 word and a label).
I did try putting the table in a table control, but that didn't do anything.|||On Dec 18, 9:43 pm, JC <J...@.discussions.microsoft.com> wrote:
> Thanks for the quick reply. The report is slightly wider than 6.5" in design
> mode to incorporate the header (which renders fine). The fields before and
> after the blank space are very short (like 1 word and a label).
> I did try putting the table in a table control, but that didn't do anything.
You're welcome. Did you mean you put it into a table control or a
rectangle control?
Enrique Martinez
Sr. Software Consultant|||Sorry. I meant that I put the table control inside the rectangle control. I
just removed all code that controls the visibility property for each row, and
the pagination problem went away.
The problem is that the customer only wants rows of the table to appear that
have data. Here's the code on the visiblity property of the tablerow:
=iif(Fields!FirstSignature.Value = string.empty, True, False)
It does work as it is supposed to, but it seems that the space is still
being allocated for the row.
BTW, it was initially written in VS 2003, but I have tried with VS 2005 with
the same results.|||On Dec 18, 11:05 pm, JC <J...@.discussions.microsoft.com> wrote:
> Sorry. I meant that I put the table control inside the rectangle control. I
> just removed all code that controls the visibility property for each row, and
> the pagination problem went away.
> The problem is that the customer only wants rows of the table to appear that
> have data. Here's the code on the visiblity property of the tablerow:
> =iif(Fields!FirstSignature.Value = string.empty, True, False)
> It does work as it is supposed to, but it seems that the space is still
> being allocated for the row.
> BTW, it was initially written in VS 2003, but I have tried with VS 2005 with
> the same results.
You might try =IIF(Fields!FirstSignature.Value = Nothing, True, False)
or =IIF(IsNothing(Fields!FirstSignature.Value), True, False)
Either should do what you want. Make sure you set the property for
the row and not the individual cells/textboxes.|||Thanks, Toolman.
I will try that too. Is using the table + row format to hide empty fields
the best practice to accomplish this? I was also going to try to set the
height to 0 if it was going to be hidden. It just seems that SSRS is taking
the empty rows into consideration when making the pagination decision.|||On Dec 19, 2:32 pm, JC <J...@.discussions.microsoft.com> wrote:
> Thanks, Toolman.
> I will try that too. Is using the table + row format to hide empty fields
> the best practice to accomplish this? I was also going to try to set the
> height to 0 if it was going to be hidden. It just seems that SSRS is taking
> the empty rows into consideration when making the pagination decision.
I believe that it is. If for no other reason than the convenience of
not having to enter the expression for each textbox/cell. Also, my
experience has been that using a table rather than a collection of
boxes just works better in general. I know that trying to hide the
entire row by hiding all the cells doesn't seem to close up the white
space.
report is a patient form that is based on a single record that is returned
from a stored procedure. Most of the records are output fine, but some
records are not paginating properly and leave 3/4 page of blank space. The
field that follows on the next page is short and should definitely fit on
that page. The report renders fine in HTML, but the requirement is a PDF
format.
The body of the report is contained in a table. Each field of the report is
contained in its own row. If the field is blank, the entire row is hidden so
that only populated data is output in the report.
In troubleshooting this, I have removed the logic that hides the rows, but
the pagination is still not correct.
I have also made sure that the data is clean and doesn't have whitespace.
Any suggestions as to how to fix this problem?
TIAOn Dec 18, 8:47 pm, JC <J...@.discussions.microsoft.com> wrote:
> I am having a pagination issue with a report when I render to PDF. The
> report is a patient form that is based on a single record that is returned
> from a stored procedure. Most of the records are output fine, but some
> records are not paginating properly and leave 3/4 page of blank space. The
> field that follows on the next page is short and should definitely fit on
> that page. The report renders fine in HTML, but the requirement is a PDF
> format.
> The body of the report is contained in a table. Each field of the report is
> contained in its own row. If the field is blank, the entire row is hidden so
> that only populated data is output in the report.
> In troubleshooting this, I have removed the logic that hides the rows, but
> the pagination is still not correct.
> I have also made sure that the data is clean and doesn't have whitespace.
> Any suggestions as to how to fix this problem?
> TIA
You will want to check the width of the report. Normally, if it is
wider than 6.5" in design view, it will wrap once exported to PDF.
Also, if you are using a table control, you will want to put it into a
rectangle control, this should shrink the extra space. Hope this
helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Thanks for the quick reply. The report is slightly wider than 6.5" in design
mode to incorporate the header (which renders fine). The fields before and
after the blank space are very short (like 1 word and a label).
I did try putting the table in a table control, but that didn't do anything.|||On Dec 18, 9:43 pm, JC <J...@.discussions.microsoft.com> wrote:
> Thanks for the quick reply. The report is slightly wider than 6.5" in design
> mode to incorporate the header (which renders fine). The fields before and
> after the blank space are very short (like 1 word and a label).
> I did try putting the table in a table control, but that didn't do anything.
You're welcome. Did you mean you put it into a table control or a
rectangle control?
Enrique Martinez
Sr. Software Consultant|||Sorry. I meant that I put the table control inside the rectangle control. I
just removed all code that controls the visibility property for each row, and
the pagination problem went away.
The problem is that the customer only wants rows of the table to appear that
have data. Here's the code on the visiblity property of the tablerow:
=iif(Fields!FirstSignature.Value = string.empty, True, False)
It does work as it is supposed to, but it seems that the space is still
being allocated for the row.
BTW, it was initially written in VS 2003, but I have tried with VS 2005 with
the same results.|||On Dec 18, 11:05 pm, JC <J...@.discussions.microsoft.com> wrote:
> Sorry. I meant that I put the table control inside the rectangle control. I
> just removed all code that controls the visibility property for each row, and
> the pagination problem went away.
> The problem is that the customer only wants rows of the table to appear that
> have data. Here's the code on the visiblity property of the tablerow:
> =iif(Fields!FirstSignature.Value = string.empty, True, False)
> It does work as it is supposed to, but it seems that the space is still
> being allocated for the row.
> BTW, it was initially written in VS 2003, but I have tried with VS 2005 with
> the same results.
You might try =IIF(Fields!FirstSignature.Value = Nothing, True, False)
or =IIF(IsNothing(Fields!FirstSignature.Value), True, False)
Either should do what you want. Make sure you set the property for
the row and not the individual cells/textboxes.|||Thanks, Toolman.
I will try that too. Is using the table + row format to hide empty fields
the best practice to accomplish this? I was also going to try to set the
height to 0 if it was going to be hidden. It just seems that SSRS is taking
the empty rows into consideration when making the pagination decision.|||On Dec 19, 2:32 pm, JC <J...@.discussions.microsoft.com> wrote:
> Thanks, Toolman.
> I will try that too. Is using the table + row format to hide empty fields
> the best practice to accomplish this? I was also going to try to set the
> height to 0 if it was going to be hidden. It just seems that SSRS is taking
> the empty rows into consideration when making the pagination decision.
I believe that it is. If for no other reason than the convenience of
not having to enter the expression for each textbox/cell. Also, my
experience has been that using a table rather than a collection of
boxes just works better in general. I know that trying to hide the
entire row by hiding all the cells doesn't seem to close up the white
space.
Saturday, February 25, 2012
Pageheight in PDF
Hello
I would like to export my report to PDF with a pageheight of 21cm.
The report itself has a pageheight of 11cm (Set in
Reportproperties-->Layout)
I dont want to use URL parameters, how do I do.
I have tried to change the Render extension in RSReportServer.Config
but to no avail. Changed it like this (<Extension Name="PDF"
Type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"
page-height="21cm"/>)
Anyone knows if this is feasible, but with another syntax?
Thanks
/MartinYou can change the page height in the report design itself. Go to Report
Properties. (Right-click the report background.)
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Martin" <martin.ekeblad@.acandofrontec.com> wrote in message
news:92af98b9.0502150132.8615bc2@.posting.google.com...
> Hello
> I would like to export my report to PDF with a pageheight of 21cm.
> The report itself has a pageheight of 11cm (Set in
> Reportproperties-->Layout)
> I dont want to use URL parameters, how do I do.
> I have tried to change the Render extension in RSReportServer.Config
> but to no avail. Changed it like this (<Extension Name="PDF"
> Type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"
> page-height="21cm"/>)
> Anyone knows if this is feasible, but with another syntax?
> Thanks
> /Martin
I would like to export my report to PDF with a pageheight of 21cm.
The report itself has a pageheight of 11cm (Set in
Reportproperties-->Layout)
I dont want to use URL parameters, how do I do.
I have tried to change the Render extension in RSReportServer.Config
but to no avail. Changed it like this (<Extension Name="PDF"
Type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"
page-height="21cm"/>)
Anyone knows if this is feasible, but with another syntax?
Thanks
/MartinYou can change the page height in the report design itself. Go to Report
Properties. (Right-click the report background.)
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Martin" <martin.ekeblad@.acandofrontec.com> wrote in message
news:92af98b9.0502150132.8615bc2@.posting.google.com...
> Hello
> I would like to export my report to PDF with a pageheight of 21cm.
> The report itself has a pageheight of 11cm (Set in
> Reportproperties-->Layout)
> I dont want to use URL parameters, how do I do.
> I have tried to change the Render extension in RSReportServer.Config
> but to no avail. Changed it like this (<Extension Name="PDF"
> Type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"
> page-height="21cm"/>)
> Anyone knows if this is feasible, but with another syntax?
> Thanks
> /Martin
Monday, February 20, 2012
Page Rendering
Appologies for the Newbie question...However here we go...
I've a report that looks just great in Visual studio, but when I export it
to pdf things go south. The page breaks that are correct in the preview are
now incorrect in the pdf and there are blank pages mingled in the report.
Does anyone have any ideas of what I can do to try to fix this.
StanYea, the page is probably too big to render it to a A4 / US Letter format
(whatever you use). You have to calculate the borders and the page width to
get the estimated output. In Germany we have the A4 format which is about 21
cm in width. If you make the viewable are about 20 cm and the borders ar
each 2 cm the page will exceed to 24 cm and a new page has to be put in
while rendering. Try to narrow the borders.
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Stan" <Stan@.discussions.microsoft.com> schrieb im Newsbeitrag
news:45B85169-EC4A-4F8A-BEA5-051A81899AA0@.microsoft.com...
> Appologies for the Newbie question...However here we go...
> I've a report that looks just great in Visual studio, but when I export it
> to pdf things go south. The page breaks that are correct in the preview
> are
> now incorrect in the pdf and there are blank pages mingled in the report.
> Does anyone have any ideas of what I can do to try to fix this.
> Stan|||I have a similar problem. Report looks great in Visual studio and in a
Browser, but when I convert it to pdf for printing, I am getting extra pages
in between with just a header printed on those pages.
I tried decrease the size of the report and make sure that it fits into 8
1/2 x 11 inches, but it did not help. I still have those annoying empty pages
in the printed report.
Any other suggestions on how can I fix it?
Thank you.
"Jens Sü�meyer" wrote:
> Yea, the page is probably too big to render it to a A4 / US Letter format
> (whatever you use). You have to calculate the borders and the page width to
> get the estimated output. In Germany we have the A4 format which is about 21
> cm in width. If you make the viewable are about 20 cm and the borders ar
> each 2 cm the page will exceed to 24 cm and a new page has to be put in
> while rendering. Try to narrow the borders.
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Stan" <Stan@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:45B85169-EC4A-4F8A-BEA5-051A81899AA0@.microsoft.com...
> > Appologies for the Newbie question...However here we go...
> >
> > I've a report that looks just great in Visual studio, but when I export it
> > to pdf things go south. The page breaks that are correct in the preview
> > are
> > now incorrect in the pdf and there are blank pages mingled in the report.
> > Does anyone have any ideas of what I can do to try to fix this.
> >
> > Stan
>
>|||Have you tried setting the page size to 8.46 by 10.46 instead of 8.5 X 11...
I have recently heard there is a bug which requires this ( until MS fixes
it.)
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Stan" <Stan@.discussions.microsoft.com> wrote in message
news:45B85169-EC4A-4F8A-BEA5-051A81899AA0@.microsoft.com...
> Appologies for the Newbie question...However here we go...
> I've a report that looks just great in Visual studio, but when I export it
> to pdf things go south. The page breaks that are correct in the preview
> are
> now incorrect in the pdf and there are blank pages mingled in the report.
> Does anyone have any ideas of what I can do to try to fix this.
> Stan
I've a report that looks just great in Visual studio, but when I export it
to pdf things go south. The page breaks that are correct in the preview are
now incorrect in the pdf and there are blank pages mingled in the report.
Does anyone have any ideas of what I can do to try to fix this.
StanYea, the page is probably too big to render it to a A4 / US Letter format
(whatever you use). You have to calculate the borders and the page width to
get the estimated output. In Germany we have the A4 format which is about 21
cm in width. If you make the viewable are about 20 cm and the borders ar
each 2 cm the page will exceed to 24 cm and a new page has to be put in
while rendering. Try to narrow the borders.
--
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Stan" <Stan@.discussions.microsoft.com> schrieb im Newsbeitrag
news:45B85169-EC4A-4F8A-BEA5-051A81899AA0@.microsoft.com...
> Appologies for the Newbie question...However here we go...
> I've a report that looks just great in Visual studio, but when I export it
> to pdf things go south. The page breaks that are correct in the preview
> are
> now incorrect in the pdf and there are blank pages mingled in the report.
> Does anyone have any ideas of what I can do to try to fix this.
> Stan|||I have a similar problem. Report looks great in Visual studio and in a
Browser, but when I convert it to pdf for printing, I am getting extra pages
in between with just a header printed on those pages.
I tried decrease the size of the report and make sure that it fits into 8
1/2 x 11 inches, but it did not help. I still have those annoying empty pages
in the printed report.
Any other suggestions on how can I fix it?
Thank you.
"Jens Sü�meyer" wrote:
> Yea, the page is probably too big to render it to a A4 / US Letter format
> (whatever you use). You have to calculate the borders and the page width to
> get the estimated output. In Germany we have the A4 format which is about 21
> cm in width. If you make the viewable are about 20 cm and the borders ar
> each 2 cm the page will exceed to 24 cm and a new page has to be put in
> while rendering. Try to narrow the borders.
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Stan" <Stan@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:45B85169-EC4A-4F8A-BEA5-051A81899AA0@.microsoft.com...
> > Appologies for the Newbie question...However here we go...
> >
> > I've a report that looks just great in Visual studio, but when I export it
> > to pdf things go south. The page breaks that are correct in the preview
> > are
> > now incorrect in the pdf and there are blank pages mingled in the report.
> > Does anyone have any ideas of what I can do to try to fix this.
> >
> > Stan
>
>|||Have you tried setting the page size to 8.46 by 10.46 instead of 8.5 X 11...
I have recently heard there is a bug which requires this ( until MS fixes
it.)
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Stan" <Stan@.discussions.microsoft.com> wrote in message
news:45B85169-EC4A-4F8A-BEA5-051A81899AA0@.microsoft.com...
> Appologies for the Newbie question...However here we go...
> I've a report that looks just great in Visual studio, but when I export it
> to pdf things go south. The page breaks that are correct in the preview
> are
> now incorrect in the pdf and there are blank pages mingled in the report.
> Does anyone have any ideas of what I can do to try to fix this.
> Stan
Page problem when exporting to pdf format.
I have a main report that contains charts and sub reports. When i see in preview mode it shows ok but when i export it in pdf format it does not show the way i want one relevant remains on previous page and other are gone to next page etc...
Another problem i am facing is if i make the page size greater than 7.5 it exports to one page blank and one page data.
One more thing i want to show table data vertically not horizontally due to restriction of 7.5 inches width.
Thanks in Advance
Muzaffar Ali
Hi Muzaffar,
Regarding report items getting shifted to next page in pdf and getting a blank page check this post -
http://blogs.msdn.com/chrisbal/archive/2006/08/10/694892.aspx
and what exactly you mean by showing data vertically, having header as rows and data as columns(then the number of columns will depend on the numbers of rows in dataset). I think you can try matrix to do that -http://blogs.msdn.com/chrishays/archive/2004/07/23/HorizontalTables.aspx
Page orientation for physical pages
Hello,
I need to design a single report (PDF) which must have both landscape and portrait orientation.
For what I know the page size is defined and static for all pages of the same report (RDL). Is there any workaround (I'm using Sql2005) ?
Thanks,
Pierre
You are right the page size defined in the rdl can't be expression and apply to all pages. One possible workaround is to use deviceinfo to specify page size and the page range. http://msdn2.microsoft.com/en-us/library/ms154682(SQL.90).aspx. For example, you can specify one page size to get page 1-3 of the report, and a different size to get a different set of pages.
|||Hello Fang,
thanks for the reply. For what I know I can define one deviceinfo setting per report. How can I define the device info setting the page 1 with a different PageHeight and PageWidth than the page 2 and 3 on the same deviceinfo ?
Thanks,
Pierre
Page numbers does not appear while exporting to PDF format
Hi there,
Page numbers does not appear while exporting to PDF format.
I have a main report containing 6 subreports each within a rectagle to
enable page breaks after each subreport. Each subreport is 7.5in wide and 10
in long. I have included same measurements for Page width and Page Height in
report properties-> layout tab also for all the 6 subreports. Here all margin
size is set to 0in.
Main report has report body (8in wide and 9.325in long) and report footer
area (8in wide and 0.175in long) with page number textbox. I have set Page
width and Page height of main report in report properties to be 8.5in wide
and 11 in long.
Spacing is set to 0in. Top and bottom margins are 0.15in each and left
margin is 0.35in and right margin is 0in. I need these marginal settings to
make my data appear good in PDF export.
With these settings, the page numbers appear at the bottom in HTML format,
but it does not appear in PDF format. What is the issue? Where am I going
wrong?
Please help me with the issue. I am using SQL Server Reporting Services 2005
RTM Version on Windows XP Service pack 2.
Thanks.Hi ringt,
Thank you for using Microsoft Partner Managed Newsgroup Support.
From your description, my understanding of this issue is: You want to show
the Page Number in the PDF render format. If I misunderstood your concern,
please feel free to let me know.
I have tested on my side, I setup a report include a subreport and set the
report representation properties like you posted. I export this report to
the PDF format, it shows the Page Number.
Would you please check does this issue occur on all the report or only for
this specified report?
If this only appeared on a specified report, would you please send the rdl
file to me? I understand the information may be sensitive to you, my direct
email address is weilu@.ONLINE.microsoft.com (Please remove the ONLINE. when
you send the email), you may send the file to me directly and I will keep
secure.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Page numbers does not appear while exporting to PDF format.
I have a main report containing 6 subreports each within a rectagle to
enable page breaks after each subreport. Each subreport is 7.5in wide and 10
in long. I have included same measurements for Page width and Page Height in
report properties-> layout tab also for all the 6 subreports. Here all margin
size is set to 0in.
Main report has report body (8in wide and 9.325in long) and report footer
area (8in wide and 0.175in long) with page number textbox. I have set Page
width and Page height of main report in report properties to be 8.5in wide
and 11 in long.
Spacing is set to 0in. Top and bottom margins are 0.15in each and left
margin is 0.35in and right margin is 0in. I need these marginal settings to
make my data appear good in PDF export.
With these settings, the page numbers appear at the bottom in HTML format,
but it does not appear in PDF format. What is the issue? Where am I going
wrong?
Please help me with the issue. I am using SQL Server Reporting Services 2005
RTM Version on Windows XP Service pack 2.
Thanks.Hi ringt,
Thank you for using Microsoft Partner Managed Newsgroup Support.
From your description, my understanding of this issue is: You want to show
the Page Number in the PDF render format. If I misunderstood your concern,
please feel free to let me know.
I have tested on my side, I setup a report include a subreport and set the
report representation properties like you posted. I export this report to
the PDF format, it shows the Page Number.
Would you please check does this issue occur on all the report or only for
this specified report?
If this only appeared on a specified report, would you please send the rdl
file to me? I understand the information may be sensitive to you, my direct
email address is weilu@.ONLINE.microsoft.com (Please remove the ONLINE. when
you send the email), you may send the file to me directly and I will keep
secure.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)