PDF Margins

I have searched through out this newsgroup and seen several people
pose the question without response. I am trying to output some reports
to PDF from the standard RS interface
(http://localserver/reports/....) The report generates a PDF
perfectly except that the margins are 1 inch on each side (I don't
know anyone that uses that setting), and can't seem to find a way to
set this at design time. I have set the page size to 8.5 / 11 and
placed everything appropriately on the design time grid. I am a
Reporting Services noob, but have written a number of applications
using various 4GL's (Delphi, VS, etc). This is my first experience
with anything .Net, so any specific guidance related to developing in
.Net should be included.Hi Kevin,
Thanks for your posting!
From your descriptions, I understood you could like to know how to set
Report Margins when rendering to PDF format. If I have misunderstood your
concern, please feel free to point it out.
Based on my knowledge, please try change the Left / Right / Top / Button
Margins number under
Report -> Report Properties -> Layout
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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.

PDF format - Garbled Data

Hello,
I searched for a response from the already posted queries. But I could not
find an answer to the problem that I have.
I have a report that looks fine on the screen and also when exported to
Excel. But
when exported to PDF some textboxes display garbled data. It may be because
of some characters in those textboxes.
Looks like a lot of people have this problem since some time. (I saw a
question that was posted last year related to the same problem)
Is there a solution to this problem?
Thanks,
SangDo you use the right font (has glyphs for these characters)? Is the font
installed on client and server?
--
Nico Cristache [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sang" <Sang@.discussions.microsoft.com> wrote in message
news:4CE82890-95A9-42E5-9D3F-CD0243FE7AE8@.microsoft.com...
> Hello,
> I searched for a response from the already posted queries. But I could
not
> find an answer to the problem that I have.
> I have a report that looks fine on the screen and also when exported to
> Excel. But
> when exported to PDF some textboxes display garbled data. It may be
because
> of some characters in those textboxes.
> Looks like a lot of people have this problem since some time. (I saw a
> question that was posted last year related to the same problem)
> Is there a solution to this problem?
> Thanks,
> Sang
>|||I am having the same problem. So far it appears to be caused by the data in
the field. If i render the report with different criteria, it comes out ok.
Im curious to see what characters are causing this. It renders perfectly in
HTML though. This is only a problem with the PDF export.
"Nico Cristache [MSFT]" wrote:
> Do you use the right font (has glyphs for these characters)? Is the font
> installed on client and server?
> --
> Nico Cristache [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Sang" <Sang@.discussions.microsoft.com> wrote in message
> news:4CE82890-95A9-42E5-9D3F-CD0243FE7AE8@.microsoft.com...
> > Hello,
> >
> > I searched for a response from the already posted queries. But I could
> not
> > find an answer to the problem that I have.
> >
> > I have a report that looks fine on the screen and also when exported to
> > Excel. But
> > when exported to PDF some textboxes display garbled data. It may be
> because
> > of some characters in those textboxes.
> >
> > Looks like a lot of people have this problem since some time. (I saw a
> > question that was posted last year related to the same problem)
> >
> > Is there a solution to this problem?
> >
> > Thanks,
> > Sang
> >
> >
>
>|||DBCS characters are unreadable in PDF format
Double byte character set (DBCS) characters may fail to display correctly in a report exported to PDF format
From http://www.developmentnow.com/g/115_2004_10_0_0_451494/PDF-format--Garbled-Data.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.comsql

PDF Export Issue

I've searched through this newsgroup for an answer to my problem, and I have
not found one:
I have a (simple?) report that consists of a standard header, body, and
footer. In the body, I have a table that outputs eight columns. The header
pulls parameters that contain default values consumed from queries, and the
footer contains simple aggregate data. The report runs and looks beautiful
in the report viewer from an ASP.NET page.
The problem manifests itself when the report is exported to a PDF. For
every page of data (there should be four), I get three pages. One of the
pages contains the table data, while the other two simply contain header and
footer data, with a blank body. As mentioned, the report looks and acts
fine in preview mode and also in Report Viewer. It is only in the exported
PDF output that I notice the issue.
I can forward a copy of the exported PDF report if that would be needed to
troubleshoot this issue, and I can provided any additional details as
needed.
Thanks in advance for any help that can be provided.
--
================================================================= William Schroeder, MCSD, CIDD
Email: william@.fanatical.usMake sure that your report is setup as follows:
(Report.PageWidth - Report.LeftMargin - Report.Right Margin) >=Body.Width
"William Schroeder" wrote:
> I've searched through this newsgroup for an answer to my problem, and I have
> not found one:
> I have a (simple?) report that consists of a standard header, body, and
> footer. In the body, I have a table that outputs eight columns. The header
> pulls parameters that contain default values consumed from queries, and the
> footer contains simple aggregate data. The report runs and looks beautiful
> in the report viewer from an ASP.NET page.
> The problem manifests itself when the report is exported to a PDF. For
> every page of data (there should be four), I get three pages. One of the
> pages contains the table data, while the other two simply contain header and
> footer data, with a blank body. As mentioned, the report looks and acts
> fine in preview mode and also in Report Viewer. It is only in the exported
> PDF output that I notice the issue.
> I can forward a copy of the exported PDF report if that would be needed to
> troubleshoot this issue, and I can provided any additional details as
> needed.
> Thanks in advance for any help that can be provided.
> --
> =================================================================> William Schroeder, MCSD, CIDD
> Email: william@.fanatical.us
>
>
>|||This worked--my body width was set to 20" for some reason.
Thank you!
--
=================================================================William Schroeder, MCSD, CIDD
Email: william@.fanatical.us
"Kevin Weir" <KevinWeir@.discussions.microsoft.com> wrote in message
news:16E48AC3-C642-4972-9185-A57FA263E420@.microsoft.com...
> Make sure that your report is setup as follows:
> (Report.PageWidth - Report.LeftMargin - Report.Right Margin) >=> Body.Width
>
>
> "William Schroeder" wrote:
> > I've searched through this newsgroup for an answer to my problem, and I
have
> > not found one:
> >
> > I have a (simple?) report that consists of a standard header, body, and
> > footer. In the body, I have a table that outputs eight columns. The
header
> > pulls parameters that contain default values consumed from queries, and
the
> > footer contains simple aggregate data. The report runs and looks
beautiful
> > in the report viewer from an ASP.NET page.
> >
> > The problem manifests itself when the report is exported to a PDF. For
> > every page of data (there should be four), I get three pages. One of
the
> > pages contains the table data, while the other two simply contain header
and
> > footer data, with a blank body. As mentioned, the report looks and acts
> > fine in preview mode and also in Report Viewer. It is only in the
exported
> > PDF output that I notice the issue.
> >
> > I can forward a copy of the exported PDF report if that would be needed
to
> > troubleshoot this issue, and I can provided any additional details as
> > needed.
> >
> > Thanks in advance for any help that can be provided.
> >
> > --
> > =================================================================> > William Schroeder, MCSD, CIDD
> >
> > Email: william@.fanatical.us
> >
> >
> >
> >
> >|||Kevin, I'm also having this same problem when exporting to .pdf. When you
write "Make sure that your report is setup as follows: (Report.PageWidth -
Report.LeftMargin - Report.Right Margin) >= Body.Width", WHERE do you code that? Thanks!
Tom
"Kevin Weir" wrote:
> Make sure that your report is setup as follows:
> (Report.PageWidth - Report.LeftMargin - Report.Right Margin) >=> Body.Width
>
>
> "William Schroeder" wrote:
> > I've searched through this newsgroup for an answer to my problem, and I have
> > not found one:
> >
> > I have a (simple?) report that consists of a standard header, body, and
> > footer. In the body, I have a table that outputs eight columns. The header
> > pulls parameters that contain default values consumed from queries, and the
> > footer contains simple aggregate data. The report runs and looks beautiful
> > in the report viewer from an ASP.NET page.
> >
> > The problem manifests itself when the report is exported to a PDF. For
> > every page of data (there should be four), I get three pages. One of the
> > pages contains the table data, while the other two simply contain header and
> > footer data, with a blank body. As mentioned, the report looks and acts
> > fine in preview mode and also in Report Viewer. It is only in the exported
> > PDF output that I notice the issue.
> >
> > I can forward a copy of the exported PDF report if that would be needed to
> > troubleshoot this issue, and I can provided any additional details as
> > needed.
> >
> > Thanks in advance for any help that can be provided.
> >
> > --
> > =================================================================> > William Schroeder, MCSD, CIDD
> >
> > Email: william@.fanatical.us
> >
> >
> >
> >
> >

PDF and new line

Here is a very funny problem and I searched, tried every method and cannot
figure this out.
Problem: If my field has carriage returns at the start and then some text
and then again carriage return, the HTML shows fine but when exported to PDF
start Carriage returns are not displayed.
Example:
Database value:
3 carriage return and this is text.
2 Carriege return and this is final text
HTML shows:
3 carriage return and this is text.
2 Carriege return and this is final text
PDF shows:
3 carriage return and this is text.
2 Carriege return and this is final text
NO INITAL carriage return in PDF but it does leave once there is some text.
Is this the rendering problem or a bug'
Note: I am not using RTRIM or TRIM anywhere.please help....
I need this resolved for today's build.
thanks,
Rahul
"RK" wrote:
> Here is a very funny problem and I searched, tried every method and cannot
> figure this out.
> Problem: If my field has carriage returns at the start and then some text
> and then again carriage return, the HTML shows fine but when exported to PDF
> start Carriage returns are not displayed.
> Example:
> Database value:
>
> 3 carriage return and this is text.
> 2 Carriege return and this is final text
>
> HTML shows:
>
> 3 carriage return and this is text.
> 2 Carriege return and this is final text
>
> PDF shows:
> 3 carriage return and this is text.
> 2 Carriege return and this is final text
>
> NO INITAL carriage return in PDF but it does leave once there is some text.
> Is this the rendering problem or a bug'
> Note: I am not using RTRIM or TRIM anywhere.|||I found it.
Replace(string, CHAR(13), CHAR(0)
PDF considers char(0), NULL ad adds a carriage return.
"RK" wrote:
> please help....
> I need this resolved for today's build.
> thanks,
> Rahul
> "RK" wrote:
> > Here is a very funny problem and I searched, tried every method and cannot
> > figure this out.
> >
> > Problem: If my field has carriage returns at the start and then some text
> > and then again carriage return, the HTML shows fine but when exported to PDF
> > start Carriage returns are not displayed.
> >
> > Example:
> >
> > Database value:
> >
> >
> >
> > 3 carriage return and this is text.
> >
> > 2 Carriege return and this is final text
> >
> >
> >
> > HTML shows:
> >
> >
> >
> > 3 carriage return and this is text.
> >
> > 2 Carriege return and this is final text
> >
> >
> > PDF shows:
> > 3 carriage return and this is text.
> >
> > 2 Carriege return and this is final text
> >
> >
> > NO INITAL carriage return in PDF but it does leave once there is some text.
> > Is this the rendering problem or a bug'
> >
> > Note: I am not using RTRIM or TRIM anywhere.sql