I have a simple report created in BIDS 2008 and deployed to a SSRS 2008 server. It has the following report properties:
page unit: Centimeters
page size:
Orientasion: Landscape
paper sise: A4
width : 29,7cm
Height: 21cm
all margins are 2,5cm
Showing and printing this report works fine on a A4 paper. Exporting to different formats works great as well, except the format I made the report for. The Word files end up with an Letter paper size or A3 size.
Does anyone have a solution for this problem?
It could be that the body width plus 5 cm (left margin plus right margin) was interpreted as being too big for A4 and so was upgraded to the next size larger (A3.) I've seen this sort of thing happen with formatting (the infamous "blank" pages in the report when viewing in print layout or exported layout) when the paper size is set to be smaller than the right margin plus the left margin plus the body width. Seems a lot of people are not even aware that the body of the report has its own sizing. Hope this helps someone out there.
Related
I'm working with CR version 13.0.25 - I believe the actual latest version as of this date is 13.0.26, so, basically the latest version of CR. What I am working with is re-positioning elements on the report dynamically from the C# code.
There are a couple of the reports where the original rpt (designed a number of years ago) spans multiple pages. These in particular are giving me issues, but they are not the only ones. The issue here focuses on the y (vertical) dimension.
CR documents use a coordinate system that is based in the upper left corner of the document, and is also based on twips (1440 twips/in). So, in theory, I should be able to set the Top value for a ReportObject to 1440 and that element should be printed 1" from some benchmark (either top of the page or bottom of the margin - I'm fairly sure it's bottom of the margin).
My results do not seem to reflect this - at least not exactly.
When I set the Top value, it appears that with some of the documents, the y dimension is scaled. In fact, I can apply a constant scaling factor (it varies according to the document) and I can make the fields appear with a relative 1" spacing all of the way to the bottom of the page. However, that scaling factor varies from document to document.
So, besides experimenting in our production code, I have also done the following:
I created a C# console app that opens an rpt file, grabs some of the elements on it, and re-positions them, then sends it to the printer. I designed a new rpt file with headers and footers sized as small as I could get them, and put 10 text fields in the details section. I iterate through the fields (via ReportDocument and ReportObjects and re-position them at 0, 1440 (1"), 2880 (2") etc.
This works perfectly with a document that has the default margins (.167 inches by default on each side). The first element has its top butted against the bottom of the margin, the second element is 1" from the top of the first element to the top of the second element, and so on down the page. If, however, I reduce the margins to zero - either programmatically or in the design, I get this scaling effect. The elements are all now about 7/8" or so apart, instead of the 1" that I would expect.
Does anyone know of any magic formula(s) or documentation on why the coordinate system appears to be changing? I could understand that if I change the margin that could offset everything on the page (assuming that the margin is our baseline) but it would seem to me that the inter-element spacing, being 1440 should still render at 1".
I believe Y is the vertical distance from the top of that section, not from the top of the page.
I am not sure how to get rid of this vertical line? is it in the margin?
and when I click the Design Tab, the page is not in full screen
The line indicates a page break when printing. Your report is designed to print on paper that is either A2 or ANSI C in size, likely with landscape orientation.
First you need to determine what size paper this report is intended to use when printing. Then go to File > Page Setup in your Crystal Report designer and configure the Printer Options and Page Options. Printer Options should either be set to No Printer, or the printer that can print the paper size you plan to use. Page Options will define the paper size, orientation and margins.
If you plan to use a paper size that is smaller than 22 inches in width, you will need to reduce the size of the objects in your report to fit the size of the paper or allow it to span multiple pages.
I have created a report in ssrs 2008 r2.It is larger then the normal A4 size .So when i export the report in word i see it clearly but when i see print preview of the report in to the word its contents get cut from the right end.I think it is due to report size. Is there any way so that we can fit the content at the time of export in to the ms word so that user can clearly take a print out in A4 size.
The only way to do this is to physically decrease the size of your report when building it as there is no auto size capability in report builder.
Right click and properties on the grey back ground. Then change the size and orientation as required.
Then click on the white body and ensure the properties bar is open. Expand the size properties option and set the size of your report to reflect the previous selection.
Also don't forget to set the margins as this will effect the amount of printable space on your report.
Lastly ensure you alter the size of you fonts and report parts to fit on the size required.
I'd love to see an automatic sizing feature in the report builder for exporting.
This is because your report content size is greater than the report size.
Report size for an A4 page is 8.5*11 inch,if your content is greater than the report size then it will move the columns to the next .
Adjust the Size of each Tablix which should be less than your report size.
Select Tablix to view properties.
expand the size option and adjust width and height accordingly.
Thanks
Just increase height and width of paper size in Report builder properties. Doesn't have any sense but it works for me.
In Report Builder in the Report Properties change the width of the report so that it exceeds the width of your data. Exporting to both Word and PDF will mean that it fits the page width. You can also adjust the height so that the report fills your desired paper size.
I am using crystal 10.2, with VS2005 .net. I have used sub report in section and given can grow true in reports. When it displays in browser it shows text vertically grows in columns, where i wanted it to grow horizontally, even if there is so much space it does not grow horizontally.
Please help me how i can do formatting horizontally.Thanks in advance.
You have to extend the field's width to fit the page's max width, then set Text Wrap option for multilines.
I created this report in iReport Professional 4.5.1 and deployed it to JasperReports Server today. The total page width is 792 pixels. In my report I have some horizontal lines that are 752 pixels wide. When I run the report in JR Server the horizontal lines stretch all the way over to the right side of my monitor. This happens when I schedule the report and ask JR Server to save it as an HTML file, but when I schedule the report and save the output as a PDF the lines are the correct size.
How can I keep the horizontal lines from stretching? The stretch type for each line is set to "no stretch." My other report elements are managing to hold their position.
Thanks,
Lisa
Try using cell borders to draw those lines instead of a static "horizontal lines."
Thanks, Sam! Your answer helped me solve this. My report is a 6-column report and I have labels that I only print in the first column. Cell borders wouldn't work because there would be lots of gaps. However, I realized that my horizontal line did not need to be 752px wide; it only needs to be slightly wider than the width of the first column and the report will take care of copying it into the subsequent columns for me. I set the horizontal lines to 127px wide and now I have an unbroken horizontal line that runs through all of my columns. I can't believe that didn't occur to me when I was creating the report in iReport.