Report viewer Page margins problem

  • Thread starter Thread starter steve
  • Start date Start date
S

steve

Hi All

I have created rdlc files and when I load them into Report Viewer at run
time they appear OK

If I click on 'Print layout' button on Report Viewer the view again appears
acceptable

If I click on 'Page setup' button the margins left & right are not what I
set on the rdlc file at design time (1.5cm) they are 5.9mm

If I click OK on the 'Page Setup' form the Report margins change to the
margins from 'Page setup'

If I open ''Page setup' again the margin settings are now less than
previously set and clicking OK results in the report margins changing again


What am I missing??


Regards
Steve
 
Further to the previous post

How can I centre the Report in the Report Viewer

Currently when I run the program the Report is left aligned in the Report
Viewer

I would like to have the Report Viewer wider than the actual report and
centred


Regards
Steve
 
Steve,

I see that Steven is answering your questions about Report Viewer.
As advice stay in the same messagethread, now it will normally takes more
than 24 hours to reply you (as he sees this) while if you had replied him
direct in the thread where he is helping you for sure would have answered
you in those 24 hours (on normal working days).

As well do we in general not like it in this newsgroup if somebody opens new
messagethreads accoording to another question already askes, we start than
again while most of the information is already given.

Cor
 
Hi Cor

Thanks for the advice

Regards
Steve
Cor Ligthert said:
Steve,

I see that Steven is answering your questions about Report Viewer.
As advice stay in the same messagethread, now it will normally takes more
than 24 hours to reply you (as he sees this) while if you had replied him
direct in the thread where he is helping you for sure would have answered
you in those 24 hours (on normal working days).

As well do we in general not like it in this newsgroup if somebody opens
new messagethreads accoording to another question already askes, we start
than again while most of the information is already given.

Cor
Click to expand...
 
Thanks for Cor's good suggestion.

Hi Steve,

I've also seen your new message in the previous thread. Since this should
be a new question and the previous one has been resolved, I think it proper
to contiue this new session in this thread. If you also feel this
comfortable, I'll close the original one and continue discussing with you
here.

As for the "page setup----> margins" issue, I've performed some tests in my
local environment, and did reproduce the same behavior as you said.
Actually, the value displayed in the "pagesetup" dialog and the original
value (set in rdlc template) is in a fixed proportion. I've just
investiaged the reportviewer's code and found that the ReportViewer control
will always perform the following calculation when migrate the margins
setting from report definition template(rdlc) to its own page settings
properties(will be displayed in page setup dialog):

=============
this.m_pageProperties = new ReportPageSettings((int)
((result1.PageProperties.PageHeight / 25.4) * 100), (int)
((result1.PageProperties.PageWidth / 25.4) * 100), (int)
((result1.PageProperties.LeftMargin / 25.4) * 100), (int)
((result1.PageProperties.RightMargin / 25.4) * 100), (int)
((result1.PageProperties.TopMargin / 25.4) * 100), (int)
((result1.PageProperties.BottomMargin / 25.4) * 100));
===============

So the /25.4 * 100 can explain the different value we encountered,
however, I still haven't got the reason of this formula(seems an incorrect
unit translation). Anyway, I'm currently consulting some other dev tools
guys on this so as to get some further information on this. I'll update
you whenever I got some new info.

Thanks for your understanding.


Regards,

Steven Cheng
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.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Hi Steve,

Sorry for keeping you waiting. Currently I'm still waiting for some update
from our product team's guys. Just post this message you let you know that
we're still focus on this issue.

Thanks for your understanding and patience.

Regards,

Steven Cheng
Microsoft MSDN Online Support Lead


==================================================

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.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Hi Steve,

Sorry for reply to you so late. We have reported this issue to our product
group and we're still investigating it. Thank you for your understanding
and patience.

Regards,
Walter Wang
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.
 
Hi Steve,

We have confirmed this is an issue of Visual Studio 2005. We have filed it
in our database and hopefully it will be fixed in Visual Studio 2005 SP1.

If this is an urgent or critical issue in your product development, I would
recommend you contact CSS (Customer Support and Service) to open a regular
support incident, so that you can request a hotfix on this issue. You can
refer to this newsgroup thread when contacting CSS and include me in the
email thread when you interact with our support engineers. I will be happy
to provide more details on this issue to the support engineer to expediate
the issue resolution process.

You may contact MSDN representatives to submit your incident online or
through phone:
http://msdn.microsoft.com/subscriptions/support/default.aspx
As an MSDN Subscriber, you are entitled to receive up to four support
incidents depending on your subscription level. But since this is a
confirmed product issue, the incident will be free.

Please feel free to post here if anything is unclear.

Regards,
Walter Wang
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.
 
Back
Top