Home Dashboard Directory Help
Search

ReportVierwer reduces the printing size if you are using the larger (150%) display's character size by FlavioR


Status: 

Closed
 as Won't Fix Help for as Won't Fix


1
0
Sign in
to vote
Type: Bug
ID: 788337
Opened: 5/21/2013 2:48:09 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description


The problem arises when you make the display’s character size larger (150%): in this case not only the ReportViewer control get wrong displaying the print preview, but it also compresses the printout on the printer (this happens even if you don’t pass through the print preview).
Details
Sign in to post a comment.
Posted by FlavioR on 11/11/2013 at 11:01 AM
Hello,
1. ...
2. if you think nobody is using "larger character size", I don't; why your os' let use it if you then don't support it?
3. which is the viable workaround you are mentioning? I don't know it, I would.
I am disappointed about this kind of "resolution".
Flavio Raimondi
Posted by Microsoft on 11/4/2013 at 6:22 PM
Hello,
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product (service packs)
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available
Thanks again for reporting the product issue and continued support in improving our product.
Matt Jones
SSRS Tiger Dev
Posted by Microsoft on 5/23/2013 at 1:42 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 5/22/2013 at 12:52 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.