.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

ReportViewer export = extra pages

Posted By:      Posted Date: September 24, 2010    Points: 0   Category :ASP.Net

 Hi, I have a report (actually several) in an ASP.NET application. The reports are landscape mode, and the RDLC file shows 11inx8.5in everywhere. In the browser, everything looks jake, but when I export to either Excel or PDF, I get extra pages. Excel gives me four pages for a one page report and PDF gives me two pages for a the same report.

I'm certain I'm missing something, but I simply can't figure out what. Anyone able to help? I can post some code if needed.

Thanks in advance

View Complete Post

More Related Resource Links

Page Header, PrintOnFirstPage=False, HTML render fine, PDF export leaves extra space

As it says in the header.Setup:SSRS 2008, VS 2008 SP1Local Mode, rdlc fileDesign:Make a 1/2" Page header with a text box in it. Set PrintOnFirstPage=FalseBody contains a Table that spans multiple "hard" pages.Results:Renders to HTML in the report viewer just fine.PDF export leaves blank 1/2" at the top of page 1. With no header for page 1, I had hoped it would remove the extra space the same as in the report viewer.Question:Any way to tell SSRS not to leave space when page header is turned off for the first page?Attempts:Tried putting everything in a rectange in the header and set the visibility to false. Still leaves space.

Repeat header rows on all pages when you export to excel sheet and print it

Hello , I need to export report into excel sheet. And when people try to print it . The header rows only appear on First page of the print . Other subsequent pages d onot have header rows. I saw another thread saying SQL server 2008 R2 will solve the issue. Can you tell me that is fixed and how to i go about configuring it on SQL server 2008 R2.   Thanks Madhavi

Sharepoint export to spreadsheet gives two extra columns in excel 2007 named as type and path, is th

When i export a list in excel 2007, it creates two extra columns named as type and path. At the same time this behaviour is not exhibited in office 2000. Is there any way to remove these two columns without using code ? Is there any configuration settings required for this, to remove it on the fly ? Thanks Ravish Verma

Preserve URL simplicity -- how to keep my pages from always having the extra "/pages" before them

Is there a way to have pages and files stay in their respective libraries but access them from different URL's?   For example, I don't want my clients to have to type "example.org/pages/contact-us.aspx". Could it just be "example.org/contact-us.aspx"???   And would I still be able to edit the pages in the browser?

ReportViewer does not export PDF correctly for wingdings fonts

I hope I am posting this in the correct forum.

We have a wpf application using the winforms reportviewer. This report shows a pass / fail status and I am using wingdings font with chr(0252) to display a tick and chr(0251) to display a cross. This works really well in the report and for sending to a printer, but when exported to pdf both the characters turn info small dots - not really acceptable for our users.

I have seen multiple other posts about this issue as a known problem, there this is a post on Microsoft connect [^] that indicates it is fixed (on 5/6/2009). See https://connect.microsoft.com/SQLServer/feedback/details/431057/ssrs-2008-sp1-ctp-pdf-export-of-wingdings-characters-above-char-127-fails

I am wondering if I am missing something obvious on how to obtain a more recent version of ReportViewer that includes a fix?

Is anyone else aware of this issue or have a resolution? As this is used in quite a few different reports, I would much prefer to fix the issue, than change all the reports t

Blank pages in SSRS Report PDF Export


I am developing a report with almost 25 columns table and the width of the report is 20pt. But I am changing the visibility of a few columns in run-time so that the resultant width will fit in one page (11pt)(I checked all the margins and resultant width of table. Sum of all the widths are with in the pagesize only). Everything is working fine when i check the report in browser, but when i try to Export to PDF there are alternate white pages, which are corresponding to the hidden columns width i guess.

How to achieve PDF Export without white pages? Also, is there any way to shrink the report to a single page?

I am using SSRS 2005

Export to Excel big size files (10000 pages) - HTTP Error 401.1



If you attempt to export a file to Excel, the browser hangs for a long time, then begins to request authorization, several times in succession .
Then displays an error message: "you are not authorized to view this page"

How To Import/Export Wiki Pages from MediaWiki


I'm looking for a way to import a MediaWiki site into a WSS 3.0's Wiki app.

I've found two ways to export wiki data from MediaWiki (the wiki engine used by Wikipedia).  There is the MediaWikiDump (a relatively simple XML format).  And then there's InstaView, which I've customised to export into WSS' Wiki format.  The latter does not offer version history, but that is not a killer problem in my case.

So, now that I have my wiki data exportable, how do I import that into WSS 3.0's Wiki database content?

I've looked for some stored procedures that are specific to the wiki data, but I'm guessing a standardized document-oriented stored-proc is being used instead.

What would you do at this point?  Are there any docs out there regarding the internals of the WSS 3.0 wiki data?  Is the doc-oriented proc (perhaps proc_AddDocument) the right way to go?  Where is the documentation on how to use proc_AddDocument?

This seems like a trivial problem that would be immensely helpful to all those "legacy" wiki-ers out there that want to transition to WSS 3.0 for their team collaboration.

Thanks in advance!

-Jonathan Boarman

Using ReportViewer.LocalReport.Render() method to export single report multiple times


I'm using the ReportViewer control on my .aspx page which displays a single report based on various user parameter selections.  Dropdown2 is dependent on the DropDown1 selection (i.e. the user selects Unit A from DropDown1 and that results in 10 selections under Dropdown2, or the user selects Unit B from DropDown1 and that results in 15 selections under DropDown2, and so on).  The user makes the selections, clicks the "Run Report" button, and the report displays as expected.  The user then can export to Excel or PDF

I've received a request to allow users to run the report for all possible selections and export to their desired format rather than having to run the report for each separate DropDown1 and DropDown2 selection.  So in other words, they don't even want to see the report on the screen, they just want to be able to click a button that runs the report for all possible parameter selections and export it to a single Excel or PDF document.

Does anyone have thoughts on how to best approach this?  Or is it even possible?  I know how to render a single report with parameters directly to PDF or Excel using the ReportViewer.LocalReport.Render() method, but I don't know how to render the same report multiple times to a single destination.

Reportviewer 2010 redistributable export to Ms Word pagenumber problem


Hi, in my asp.net app I use the Reportviewer 2010 tot show reports (RDLC). This is working fine, but when I export to Word the pagenumbers is always 1 from 1 even when the document contains 2 or more page, while when I export to PDF it is showing the right page number.

Anyone has the same problem?

Disable Export Options on ReportViewer using a Server Report


Is it possible to disable export options on a server report in the ReportViewer control without changing the reportserver.config file? 

I have the code to change a Local Report but not a Server Report.  We have a group of reports we only want to be able to export to PDF and TIFF while the other server reports should be exportable in all formats.

Export Visio Database Table Names to Excel

If you use the Enterprise Architect edition of Microsoft Visio for data modeling regularly, then there is a good chance that at some point you've wanted to export just the table names into Excel. You might want to do this to map logical ERD entities to physical data model tables, track project status by entity, or track overlap between database versions.

High Performance ASP.NET - Speeding Up ASP.NET Pages

have been writing a series of blog posts, which I have named High Performance ASP.NET Websites Made Easy! There is no rhyme or reason to the order of these posts and certainly can be read in any order:

Developing High Performance and Scalable ASP.NET Websites
Avoid Chatty Interfaces Between the Tiers in Your ASP.NET Web Application
ASP.NET Page Profiling - Page Tracing - High Performance and Scalable ASP.NET Websites Made Easy
Web Applications: N-Tier vs. N-Layer - Benefits and Trade-Offs
Query Analyzer - Sql Server Database Indexes and Execution Plans

SharePoint Application and Site Pages - Part 1 of 2

In this first part of the two part series, Steven covers the differences between Site and Application pages in SharePoint 2007, why each may be used in various circumstances, and prepares for the construction of a menu located application page. After a brief introduction he examines the concept of Site Pages and Application Pages separately in detail with supported screenshots.

SharePoint Application and Site Pages - Part 2 of 2

As the second article in a two part series, Steven examines the attributes and details of a SharePoint 2007 application page, including the construction and feature deployment of the same page based project. Since this is a WSS level objective, as opposed to MOSS, you will not need MOSS to work with the code included in this project. Windows Server 2003, WSS, and Visual Studio 2005 are all that is needed, with no additional add-ons. He provides a detailed analysis of each step involved in the creation and deployment of the project.

Application Vs. Content Pages in SharePoint

SharePoint has two types of ASPX pages. One type is the application page, also known as a _layout page. The other type of ASPX page is a content page, also known as a site page. Each of these page types is stored in a different location in SharePoint. When developers create custom ASPX pages, they must decide on the page type.

Export SharePoint List to Excel Spreadsheet Programmatically using C#

In SharePoint applications, Custom Lists are used to store business data and Document Libraries to store the documents. But for data manupulation and analysis, Microsoft Excel provides very rich features as compared to SharePoint Lists. That's why people still loves to work on Microsoft Excel Sheets.
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend