Export Report to File: February 2012

Sunday, February 26, 2012

Export to Excel Problem

Hi,
i am facing a problem to export data to MS Excel.
In the financial report, I have month and date from 9/1/1998 to present
(hardcode all the column).
Users would like to export those data into an Excel spreadsheet.
However, if users choose the date from 1/1/2003 to 1/1/2004 then all the
date before 1/1/2003 will become one big blank/empty column since the width
of the report doesn't change. when all data are exported to the Excel
spreadsheet, that big blank/empty column generates an error and it said
"Excel Rendering Extension : Width of excel cell in the excel sheet exceeded
the maximum limit of 1726.5 Points."
Does anyone see this kind of error before or any suggestion/idea about how
to fix this problem.
Many thanks
EdPlease check this thread:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=8541dc14-86f5-4ea5-a764-802433a51e2b&sloc=en-us
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ed" <Ed@.discussions.microsoft.com> wrote in message
news:B1E76E31-D461-4D21-96BB-A6B8297044E5@.microsoft.com...
> Hi,
> i am facing a problem to export data to MS Excel.
> In the financial report, I have month and date from 9/1/1998 to present
> (hardcode all the column).
> Users would like to export those data into an Excel spreadsheet.
> However, if users choose the date from 1/1/2003 to 1/1/2004 then all the
> date before 1/1/2003 will become one big blank/empty column since the
width
> of the report doesn't change. when all data are exported to the Excel
> spreadsheet, that big blank/empty column generates an error and it said
> "Excel Rendering Extension : Width of excel cell in the excel sheet
exceeded
> the maximum limit of 1726.5 Points."
> Does anyone see this kind of error before or any suggestion/idea about how
> to fix this problem.
> Many thanks
> Ed
>

Export to Excel Problem

When I try to export a report to Excel I get the following message:
"Internet Explorer was not able to open this internet site. The requested
site is either unavailable or cannot be found. Please try again later."
The report renders fine and will export to a pdf with no errors.
Anyone have any suggestions?
ThanksDo you have Excel on the machine you are trying to export Excel?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"sperotti" <sperotti@.discussions.microsoft.com> wrote in message
news:A2B259A6-2DD3-4BE3-8DD9-A0242F8E13C5@.microsoft.com...
> When I try to export a report to Excel I get the following message:
> "Internet Explorer was not able to open this internet site. The requested
> site is either unavailable or cannot be found. Please try again later."
> The report renders fine and will export to a pdf with no errors.
> Anyone have any suggestions?
> Thanks
>|||Yes. I have Excel 2003.
"Bruce L-C [MVP]" wrote:
> Do you have Excel on the machine you are trying to export Excel?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "sperotti" <sperotti@.discussions.microsoft.com> wrote in message
> news:A2B259A6-2DD3-4BE3-8DD9-A0242F8E13C5@.microsoft.com...
> > When I try to export a report to Excel I get the following message:
> >
> > "Internet Explorer was not able to open this internet site. The requested
> > site is either unavailable or cannot be found. Please try again later."
> >
> > The report renders fine and will export to a pdf with no errors.
> >
> > Anyone have any suggestions?
> >
> > Thanks
> >
>
>

Export To Excel problem

Hi,
When I select the export to excel file format, I get the following in the
excel file:
"Data Regions within table/matrix cells are ignored".
Is this a known bug in RS..
Any info will be appreciated.
Thanks
SureshHi,
The message tells you exactly how the Excel export does with data regions
encapsulated in tables/matrixes. The same is for subreports.
This behavior is by design.
--
| Jan Pieter Posthuma
--
"Suresh" wrote:
> Hi,
> When I select the export to excel file format, I get the following in the
> excel file:
> "Data Regions within table/matrix cells are ignored".
> Is this a known bug in RS..
> Any info will be appreciated.
> Thanks
> Suresh
>

export to excel percentage problem

If you format a number in SRS to a percentage using P0 format then export to
excel it left aligns the percentage and reads it as text.
Is there anyway to export to excel and it automatically reads it correctly
as a percentage?I used the formatting code "0.0%" rather than the predefined code and it
exports to Excel correctly.
Colin
"GeoffF" <GeoffF@.discussions.microsoft.com> wrote in message
news:9952F576-F34E-4AE0-B8B8-A499F69B345A@.microsoft.com...
> If you format a number in SRS to a percentage using P0 format then export
> to
> excel it left aligns the percentage and reads it as text.
> Is there anyway to export to excel and it automatically reads it correctly
> as a percentage?

Export to excel number formatting problem

Hi,

when i try to export reports to excel number fileds has exported as text !!

I use SQL server with database in US codepage, Reporting Services in english version but excel with Italian codepage settings.

So i must convert the defaul decimal separator from "." to "," within the report generation. This cause that i can't use te cdbl() conversion directly in the report field.

Anyone have sugestion ?

P.S. I can't change the database and excel codepage settings

hi,

Please read this article: http://blogs.msdn.com/bimusings/archive/2007/01/11/happiness-is-automatic-sql-reporting-services-localization.aspx

I also used it.

regards,

Janos

|||

SOLVED !!!!

Thank you

Export to Excel -multiple sheets

Hi,

I am using .rdlc report in ASP.NET 2.0.

My report consists of 10 subreport and 1 main report. I want to export each subreport in separate sheets like Shee1 is Subreport1 and Sheet2 is Subreport2 etc... How can i do this.

Thanks.

The Excel renderer creates new worksheet tabs for each page in your report. To get a new page for each Subreport, put each of them inside a Rectangle and set PageBreakAtStart on the Rectangle to True.

-Chris

|||

I haven't been able to get the sub reports to show when exported to excel. Is there a trick to this?

Dwayne

|||

This works for me. However, what does not work, is using a subreport in a cell of a table and export that to Excel.

Regards, Jeroen

Export to Excel -multiple sheets

Hi,

I am using .rdlc report in ASP.NET 2.0.

My report consists of 10 subreport and 1 main report. I want to export each subreport in separate sheets like Shee1 is Subreport1 and Sheet2 is Subreport2 etc... How can i do this.

Thanks.

-Chris

|||

I haven't been able to get the sub reports to show when exported to excel. Is there a trick to this?

Dwayne

|||

This works for me. However, what does not work, is using a subreport in a cell of a table and export that to Excel.

Regards, Jeroen

|||Hi, related to Jeroen's Question...
"This works for me. However, what does not work, is using a subreport in a cell of a table and export that to Excel."

As a solution for this problem, we can have a rectangle within the table and place the subreport inside it, it allows to export. There is again few limitaions further but at least we can export the data of the subreport. Hope this helps.

Export to Excel -multiple sheets

Hi,

I am using .rdlc report in ASP.NET 2.0.

My report consists of 10 subreport and 1 main report. I want to export each subreport in separate sheets like Shee1 is Subreport1 and Sheet2 is Subreport2 etc... How can i do this.

Thanks.

-Chris

|||

I haven't been able to get the sub reports to show when exported to excel. Is there a trick to this?

Dwayne

|||

This works for me. However, what does not work, is using a subreport in a cell of a table and export that to Excel.

Regards, Jeroen

Export to Excel missing last row

We have several reports in Excel that display fine in HTML, but when they
are exported to Excel the last Row is missing. There is a post dated 9/7 that
mentions the same problem, but was never answered...does anyone have any idea
what might be causing this or if there is a workaround?
ThanksI am having the same issue. I see there have been other posts about the
topic, but no answers. Anyone know any way to fix this? Thanks.
"kbradfor" wrote:
> We have several reports in Excel that display fine in HTML, but when they
> are exported to Excel the last Row is missing. There is a post dated 9/7 that
> mentions the same problem, but was never answered...does anyone have any idea
> what might be causing this or if there is a workaround?
> Thanks|||I made post on 10/14 and 10/20 with no replies. I'm hoping that Microsoft
will respond soon. This problem is causing my client to question the
reporting engine.
"kbradfor" wrote:
> We have several reports in Excel that display fine in HTML, but when they
> are exported to Excel the last Row is missing. There is a post dated 9/7 that
> mentions the same problem, but was never answered...does anyone have any idea
> what might be causing this or if there is a workaround?
> Thanks|||Has anyone tried to add a blank footer row to the table? This way if the bug
does occur it will just drop a blank footer and not your data. (I know this
is idea is just a band-aid not a fix but MS seems to be ignoring this
problem.)
I have not tested this theory myself because I have only seen this happen a
few times and each time I tried to dup the results everything worked fine.
Maybe someone out there has a report that has a regular problem that could
test it for me?
Tim
"Derek Howard" wrote:
> I made post on 10/14 and 10/20 with no replies. I'm hoping that Microsoft
> will respond soon. This problem is causing my client to question the
> reporting engine.
> "kbradfor" wrote:
> >
> > We have several reports in Excel that display fine in HTML, but when they
> > are exported to Excel the last Row is missing. There is a post dated 9/7 that
> > mentions the same problem, but was never answered...does anyone have any idea
> > what might be causing this or if there is a workaround?
> >
> > Thanks

Export to Excel madness

Why is it when I export a series of textboxes, all of which have the same
height and top, and each one whose left position is exactly equal to the
left position plus the width of the textbox to the left, they do not export
to a single row in Excel? And not just that, but they'll be *half* a row
off, such that one textbox may span Excel rows 10 and 11, while its neighbor
is on rows 11 and 12? Grids seem to handle this ok, but when you want
something as simple as putting a row of textboxes in the page header to line
up above values in the grid, it makes managers very unhappy when they get
their spreadsheet and the headers are not in a straight line.I should add that TIFF and PDF turns out beautifully, and Web Archive is a
little screwy, but not nearly as bad.
"DJM" <msnews@.puddlestheshark.com> wrote in message
news:OYc4vq1TFHA.3152@.TK2MSFTNGP12.phx.gbl...
> Why is it when I export a series of textboxes, all of which have the same
> height and top, and each one whose left position is exactly equal to the
> left position plus the width of the textbox to the left, they do not
> export to a single row in Excel? And not just that, but they'll be *half*
> a row off, such that one textbox may span Excel rows 10 and 11, while its
> neighbor is on rows 11 and 12? Grids seem to handle this ok, but when you
> want something as simple as putting a row of textboxes in the page header
> to line up above values in the grid, it makes managers very unhappy when
> they get their spreadsheet and the headers are not in a straight line.
>|||I have the same problem :|||I think the problem is the report-head-line's width, try to modify it to the
same as the first column or the same as total clumns.
"DJM" wrote:
> Why is it when I export a series of textboxes, all of which have the same
> height and top, and each one whose left position is exactly equal to the
> left position plus the width of the textbox to the left, they do not export
> to a single row in Excel? And not just that, but they'll be *half* a row
> off, such that one textbox may span Excel rows 10 and 11, while its neighbor
> is on rows 11 and 12? Grids seem to handle this ok, but when you want
> something as simple as putting a row of textboxes in the page header to line
> up above values in the grid, it makes managers very unhappy when they get
> their spreadsheet and the headers are not in a straight line.
>
>|||When I design a report for Excel I do the following. I add an extra table
header row (or multiple). Then you can merge cells appropriately, do any
left/right/center lining up and have what I would normally use textboxes
for. This should get around your problem but more importantly it prevents
the issue where the excel created has the cells created such that you can
still sort appropriately. If you have textboxes above your table then you
can end up with Excel sheet where you cannot sort.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Eric Wang" <Eric Wang@.discussions.microsoft.com> wrote in message
news:8BB5219A-DD84-4308-B99A-1602FC6662E8@.microsoft.com...
>I think the problem is the report-head-line's width, try to modify it to
>the
> same as the first column or the same as total clumns.
> "DJM" wrote:
>> Why is it when I export a series of textboxes, all of which have the same
>> height and top, and each one whose left position is exactly equal to the
>> left position plus the width of the textbox to the left, they do not
>> export
>> to a single row in Excel? And not just that, but they'll be *half* a row
>> off, such that one textbox may span Excel rows 10 and 11, while its
>> neighbor
>> is on rows 11 and 12? Grids seem to handle this ok, but when you want
>> something as simple as putting a row of textboxes in the page header to
>> line
>> up above values in the grid, it makes managers very unhappy when they get
>> their spreadsheet and the headers are not in a straight line.
>>

Export to Excel Link - Inactive -Critical - Need Help

Hi all,
I am using asp.net control(Reportviewer) to view the report in the web, but
when I render the report, the export link is inactive and when I choose the
refresh button, the Export link is activated.
For the first time the Export link button is inactive.
This issue is very critical, please need your help
Thanks
Balaji
--
Message posted via http://www.sqlmonster.comCan anyone answer this.
Balaji
--
Message posted via http://www.sqlmonster.com

Export to Excel Legal Landscape

I created a Landscape Report for Legal Paper. When I export the report to
Excel the report appears in Excel as Landscape for 8.5X11.
Does anyone know how I can resolve this issue?Have you tried changing the report page size to 8.5x14?
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"sturmill" <sturmill@.discussions.microsoft.com> wrote in message
news:164F62F5-44A5-4A89-9132-D647DC10D538@.microsoft.com...
>I created a Landscape Report for Legal Paper. When I export the report to
> Excel the report appears in Excel as Landscape for 8.5X11.
> Does anyone know how I can resolve this issue?|||Are you refering to the page size in the print dialog box for excel or the
page size in the report server. I have changed the page size in the report
server to 8.5 x 14.
Same results. Exports landscape to excel but size 8.5X11.
"Jeff A. Stucker" wrote:
> Have you tried changing the report page size to 8.5x14?
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "sturmill" <sturmill@.discussions.microsoft.com> wrote in message
> news:164F62F5-44A5-4A89-9132-D647DC10D538@.microsoft.com...
> >I created a Landscape Report for Legal Paper. When I export the report to
> > Excel the report appears in Excel as Landscape for 8.5X11.
> >
> > Does anyone know how I can resolve this issue?
>
>|||Report server. Does it export to PDF or TIFF legal size correctly? Just
curious...
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"sturmill" <sturmill@.discussions.microsoft.com> wrote in message
news:D879AC34-A597-409F-9493-BAACB0489FEE@.microsoft.com...
> Are you refering to the page size in the print dialog box for excel or the
> page size in the report server. I have changed the page size in the report
> server to 8.5 x 14.
> Same results. Exports landscape to excel but size 8.5X11.
>
> "Jeff A. Stucker" wrote:
>> Have you tried changing the report page size to 8.5x14?
>> --
>> Cheers,
>> '(' Jeff A. Stucker
>> \
>> Business Intelligence
>> www.criadvantage.com
>> ---
>> "sturmill" <sturmill@.discussions.microsoft.com> wrote in message
>> news:164F62F5-44A5-4A89-9132-D647DC10D538@.microsoft.com...
>> >I created a Landscape Report for Legal Paper. When I export the report
>> >to
>> > Excel the report appears in Excel as Landscape for 8.5X11.
>> >
>> > Does anyone know how I can resolve this issue?
>>|||If I go into print setup in PDF it works and TIFF works. I have gone into
Print Setup for excel and set to legal and it still doesn't work. Any other
thoughts?
"Jeff A. Stucker" wrote:
> Report server. Does it export to PDF or TIFF legal size correctly? Just
> curious...
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "sturmill" <sturmill@.discussions.microsoft.com> wrote in message
> news:D879AC34-A597-409F-9493-BAACB0489FEE@.microsoft.com...
> > Are you refering to the page size in the print dialog box for excel or the
> > page size in the report server. I have changed the page size in the report
> > server to 8.5 x 14.
> > Same results. Exports landscape to excel but size 8.5X11.
> >
> >
> > "Jeff A. Stucker" wrote:
> >
> >> Have you tried changing the report page size to 8.5x14?
> >>
> >> --
> >> Cheers,
> >>
> >> '(' Jeff A. Stucker
> >> \
> >>
> >> Business Intelligence
> >> www.criadvantage.com
> >> ---
> >> "sturmill" <sturmill@.discussions.microsoft.com> wrote in message
> >> news:164F62F5-44A5-4A89-9132-D647DC10D538@.microsoft.com...
> >> >I created a Landscape Report for Legal Paper. When I export the report
> >> >to
> >> > Excel the report appears in Excel as Landscape for 8.5X11.
> >> >
> >> > Does anyone know how I can resolve this issue?
> >>
> >>
> >>
>
>|||I am still having this issue. Is this something that will be fixed in the
next service pack? My CFO's and CEO's are getting fustrated having to do
multiple steps to print the exported document in Legal Landscape.
"sturmill" wrote:
> If I go into print setup in PDF it works and TIFF works. I have gone into
> Print Setup for excel and set to legal and it still doesn't work. Any other
> thoughts?
> "Jeff A. Stucker" wrote:
> > Report server. Does it export to PDF or TIFF legal size correctly? Just
> > curious...
> >
> > --
> > Cheers,
> >
> > '(' Jeff A. Stucker
> > \
> >
> > Business Intelligence
> > www.criadvantage.com
> > ---
> > "sturmill" <sturmill@.discussions.microsoft.com> wrote in message
> > news:D879AC34-A597-409F-9493-BAACB0489FEE@.microsoft.com...
> > > Are you refering to the page size in the print dialog box for excel or the
> > > page size in the report server. I have changed the page size in the report
> > > server to 8.5 x 14.
> > > Same results. Exports landscape to excel but size 8.5X11.
> > >
> > >
> > > "Jeff A. Stucker" wrote:
> > >
> > >> Have you tried changing the report page size to 8.5x14?
> > >>
> > >> --
> > >> Cheers,
> > >>
> > >> '(' Jeff A. Stucker
> > >> \
> > >>
> > >> Business Intelligence
> > >> www.criadvantage.com
> > >> ---
> > >> "sturmill" <sturmill@.discussions.microsoft.com> wrote in message
> > >> news:164F62F5-44A5-4A89-9132-D647DC10D538@.microsoft.com...
> > >> >I created a Landscape Report for Legal Paper. When I export the report
> > >> >to
> > >> > Excel the report appears in Excel as Landscape for 8.5X11.
> > >> >
> > >> > Does anyone know how I can resolve this issue?
> > >>
> > >>
> > >>
> >
> >
> >

export to excel issues

can anyone explain, why when exporting a really simple spread to excel, one ends up with a ton of blank rows?

I have a report with 8 columns but when exporting to excel i end up with around 50 columns. All most are blank?

That is because Excel uses a whole lot of column merging to get the alignment as close as possible to the original report. It sounds like you have unmerged the columns/cells or have tried to copy and paste to another worksheet.

A simple way to fix this is to unmerge the cells, then copy just the columns you are interested in, or delete the blank columns altogether.

|||this may because of formating issues .try to format the fields properly or try to make some changes(like reduce or increase text size etc) in each field.|||

I'm not sure if you're seeing extra columns or rows or both, but it could be due to the size of your background (the white grid space in the body of the report). Make sure it is not bigger than your report items. I always get extra columns and rows in a dark grey in Excel if I don't size it correctly.

-Marianne

Export to excel issue

I Have a report, in SQL Reporting servies. THE report has a field where the value shows up as an integer ie 0. However, when the report is exported to excel, the field value shows up as a decimal ie 0.4.

How do i keep the number to show as an integer only ie 0, when exported to excel.

Are you specifying a format code to only display the integer, or is the underlying value actually an integer? If it is the former, what is the format code you are using?

Ian|||Yes, I am specifying a format code of F0 on that textbox for that field.|||Tarana,

This seems like a bug; however, the good news is there is a workaround: try the following format code.

##0

Ian|||Thanks a bunch Ian- that worked very well.

Export to Excel in MS Access

Hi,

I have one form in access application which shows various fields from
the database. The fields are like No of PCs a client has,No of
employees,revenue etc.

Need of the user is to filter the data on the form and export the
results.
I am using a Qury as the base for this form.Can I do it easily or i
need to write the code to do this.

Secondly can I provide a separate interface to allow user to Query and
extract the data.

Say, PC between <SomeRange> AND/ OR
Revenue Between <Some Range
whatever result comes will be exported to the Excel file.

Please tell me if you have any solution.

Thanks in Advance.

Rohit

--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbforumz.com/General-Dis...pict241673.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=840002If you can utilize a query to create the data you want, then you can do
a simple trick of exporting the data within Access to Excel with very
little code.

DoCmd.OutputTo acOutputQuery, "Name Of Query", acFormatXLS

This can be assigned to a button and you have your results. This works
great if the query is based off the actual form.

Enjoy!

export to excel has merged cell problem

I have noticed that after my report exported to excel, some of the cells are
merged.
For example, I have report as following
ID Project Name Author Description
1 xxxx dfdf fdfdfdfd
after export in the excel, the data shows correctly, but on the top of the
excel file, it may show something like this
A B C D E F
ID Project Name Author Description
1 xxxx dfdf fdfdfdfd
The problem is some of the columns has one column data but excel treat them
as two columns.
Does anyone have any idea? thanks.The Excel renderer will merge cells in order to preserve the report item
alignment you defined when you designed the report.
Merging usually happens when there are report items either below or above
the table whose left or right edges do not exactly match that of the table
cells below.
A classic example of this is a single textbox above a table that functions
as a header. Make sure this textbox starts and ends at the border of one of
the below table's cells.
Best,
-Chris
SQL Server Reporting Services
"Helen" <Helen@.discussions.microsoft.com> wrote in message
news:8EDC7FB7-BC51-473E-A29B-4CDB47E9C4F4@.microsoft.com...
>I have noticed that after my report exported to excel, some of the cells
>are
> merged.
> For example, I have report as following
> ID Project Name Author Description
> 1 xxxx dfdf fdfdfdfd
> after export in the excel, the data shows correctly, but on the top of the
> excel file, it may show something like this
> A B C D E F
> ID Project Name Author Description
> 1 xxxx dfdf fdfdfdfd
> The problem is some of the columns has one column data but excel treat
> them
> as two columns.
> Does anyone have any idea? thanks.
>

Export To Excel Gives Me Gray Cells

I have a report which was in RS 2003 and exported to Excel fine. Now when I export the same report using RS 2005 to Excel I get gray cells at the bottom of each table. I have the background of the body set to transparent. I have tried setting the background of the body to white and other colors. Those colors show up but the gray is still there as well. In preview mode and export to pdf I do not have those problems. Basically gray cells are showing up where they should not be. Any help would be great.Do you have anything in the table footer/s?|||I do have items in the footer. Now here is the kicker. When I take the color out of the header of the top most table then the background goes to white and all the other tables retain their color. the space between the tables when exported to excel take on the color of what ever the color is set to as the background color in the topmost table on the report. This is one to mark up as weird but true.|||To be even more specific all space between tables on the report when exported to excel, that space takes on the color of the background color of the first textbox of the header of the top most table. Can anyone explain this one to me.|||I found a work around for this. Not sure of what is going on but I put a blank row about the table header row of the top most table. Set its height to minimum and made its background transparent and it cleared up my problem. Maybe one day I will figure out what is happing in the rendering process.

Export To Excel Funny Result post Sp1

Hi
I have a report with which looked fine on the web page, and rendered to pdf.
But when export to excel, the cells are not alligned on the same row as the
report should be. It goes up and down 1 row randomly. The whole report just
look like zig zag mesh. Any one experience this issue?
Another issue is objects such as lists and text box where visibility are
toggled with an expression exports randomly. Some visible item are not
exported.
My report is a buch of list and text boxes align into rows. but as i said
before, after export to excel, each cell in the row randomly goes up and down
one row like a zig zag.
Any tips are appreciated.Sounds like the item spacing is interpreted as overlapping by the
export engine.
I'm having tons of fun with this same behavior right now. Spent 6
hours on it yesterday and today with unsatisfactory results. Boss
says "the users will have to live with it." Export results to PDF and
Excel are not consistent with each other, nor with HTML view, nor with
devenv preview. You have to strive for a balanced compromise, and one
at least of the views will look funky if you try to butt each item up
against another.
Don't depend on the design surface for item location and size. Even a
grid size of .025in won't help. Use the numbers in the properties box
for best results. For HTML rendering at least, the smallest size
increment that has meaning (according to BOL) is 0.2mm = 0.0078740 in,
round to 0.008in for use.
See "Design Considerations for Rendering" in the Books Online,
especially "Designing for Microsoft Excel Output."
EtU
happy for correction by the more knowledgeable
>Hi
>I have a report with which looked fine on the web page, and rendered to pdf.
>But when export to excel, the cells are not alligned on the same row as the
>report should be. It goes up and down 1 row randomly. The whole report just
>look like zig zag mesh. Any one experience this issue?
>Another issue is objects such as lists and text box where visibility are
>toggled with an expression exports randomly. Some visible item are not
>exported.
>My report is a buch of list and text boxes align into rows. but as i said
>before, after export to excel, each cell in the row randomly goes up and down
>one row like a zig zag.
>Any tips are appreciated.

Export to Excel Functionality (SQL RS 2005)?

Hi there,
We have an ASP.NET 2.0 application that we are currently using and
would like to tie in some SQL RS 2005 functionality. Specifically,
we'd like to be able to use the report exporting functionality to
generate Excel or Acrobat docs, without having to use the report
viewer or using Reporting Services to generate a report in any way
that would be sent to the client. In other words, we don't want
reporting services to display the report on the site in any way, we
just want it to return the doc type selected from a drop down list.
Is this possible?
Thanks in advance,
RichReporting services is built totally on web services. This is used by
everything you see. For instance, Report Manager (the portal that ships with
RS uses it). In 2005 the reportviewer control uses it. It is totally
documented and you can use it in your app and render to whatever format you
like (html, csv, excel, pdf etc). You stream it back to your app and then do
with it as you please.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"rchung77" <rich.chung@.gmail.com> wrote in message
news:1186758560.748324.102890@.e9g2000prf.googlegroups.com...
> Hi there,
> We have an ASP.NET 2.0 application that we are currently using and
> would like to tie in some SQL RS 2005 functionality. Specifically,
> we'd like to be able to use the report exporting functionality to
> generate Excel or Acrobat docs, without having to use the report
> viewer or using Reporting Services to generate a report in any way
> that would be sent to the client. In other words, we don't want
> reporting services to display the report on the site in any way, we
> just want it to return the doc type selected from a drop down list.
> Is this possible?
> Thanks in advance,
> Rich
>

Export to Excel from SQL Server 2000

I was wondering if anyone knew how I could export data from SQL Server to a specific Excel worksheet with an Excel file, such as "Sheet2" or "Sheet3" for example, instead of dropping the data automatically in to Sheet1.
Thank you!
DaveI was wondering if anyone knew how I could export data from SQL Server to a specific Excel worksheet with an Excel file, such as "Sheet2" or "Sheet3" for example, instead of dropping the data automatically in to Sheet1.

Thank you!

Dave

Use Import/Export wizard and specify Sheet2$ as the destination.|||Look into setting up an ODBC connection...

You can create the proper view (or sproc) in SQL Server (and even pass parameters) and setup Excel to pull the data from SQL Server when right-click the external data source and choose to Refresh Data.

I've used it for yours to distribute real-time reporting solutions. Just created the worksheet, set everybody up with the ODBC and they can refresh as often as they like. I use it to provide up to the minute performance on manufacturing facilities. A real eye-opener for my clients.

Let me know if you want more specific information. Best of luck,

Alex

Export to excel from report manager problem

When i use export from report manager to excel for some reason it gave us
that error
but one thing more i used open that report using visual studio on my friend
computer and then preview the report and then select save as excel file . it
didnt give me error but when i use report manager and then try to export to
excel has that error
Microsoft Excel File Repair Log
Errors were detected in file C:\test.xls'
The following is a list of repairs:
Damage to the file was so extensive that repairs were not possible. Excel
attempted to recover your formulas and values, but some data may have been
lost or corrupted.Hello Amjad.
I've seen this before. This happened when i had certain formulas in my
report, either in text boxes or in a chart. Are you using any complex
formulas? If you are, take them out temporarily, and try to export the
file. Let me know if it works.
Amjad wrote:
> When i use export from report manager to excel for some reason it gave us
> that error
> but one thing more i used open that report using visual studio on my friend
> computer and then preview the report and then select save as excel file . it
> didnt give me error but when i use report manager and then try to export to
> excel has that error
> Microsoft Excel File Repair Log
> Errors were detected in file C:\test.xls'
> The following is a list of repairs:
> Damage to the file was so extensive that repairs were not possible. Excel
> attempted to recover your formulas and values, but some data may have been
> lost or corrupted.|||Thanks
Yeah i was using a two charts but for certain reason for one year as year
was my parameter did give me any error and for another year data it gave me
error to open affter export. then i removed the chart and after that it didnt
actually i was using two chart , removing either of one solved the problem
but i need to include these chart back but due to that problem i removed it
temprarly....
Do you have any solution or any hot fix availabe to solve this problem.
because on of my friend computer it did export from visual studio preview
option not from report manager but on my computer it did not export both from
visual studio and report manager. it seem that his computer got some updates
for visual studio that i am missing thats why its giving me that problem even
from visual studio preview option. so if we find that hotfix so i can install
both on report manager server and my local computer...
"KevinGreen24@.gmail.com" wrote:
> Hello Amjad.
> I've seen this before. This happened when i had certain formulas in my
> report, either in text boxes or in a chart. Are you using any complex
> formulas? If you are, take them out temporarily, and try to export the
> file. Let me know if it works.
>
> Amjad wrote:
> > When i use export from report manager to excel for some reason it gave us
> > that error
> > but one thing more i used open that report using visual studio on my friend
> > computer and then preview the report and then select save as excel file . it
> > didnt give me error but when i use report manager and then try to export to
> > excel has that error
> >
> > Microsoft Excel File Repair Log
> >
> > Errors were detected in file C:\test.xls'
> > The following is a list of repairs:
> >
> > Damage to the file was so extensive that repairs were not possible. Excel
> > attempted to recover your formulas and values, but some data may have been
> > lost or corrupted.
>|||OK. Put the charts back in, and try to export again.
I'm not exactly sure of any hotfixes right now. If there's any service
packs / patches out there for MSRS 2005 you should install them. But
I'm not positive there are any. I'm sorry I couldn't be of more help.
Amjad wrote:
> Thanks
> Yeah i was using a two charts but for certain reason for one year as year
> was my parameter did give me any error and for another year data it gave me
> error to open affter export. then i removed the chart and after that it didnt
> actually i was using two chart , removing either of one solved the problem
> but i need to include these chart back but due to that problem i removed it
> temprarly....
> Do you have any solution or any hot fix availabe to solve this problem.
> because on of my friend computer it did export from visual studio preview
> option not from report manager but on my computer it did not export both from
> visual studio and report manager. it seem that his computer got some updates
> for visual studio that i am missing thats why its giving me that problem even
> from visual studio preview option. so if we find that hotfix so i can install
> both on report manager server and my local computer...
>
> "KevinGreen24@.gmail.com" wrote:
> > Hello Amjad.
> >
> > I've seen this before. This happened when i had certain formulas in my
> > report, either in text boxes or in a chart. Are you using any complex
> > formulas? If you are, take them out temporarily, and try to export the
> > file. Let me know if it works.
> >
> >
> > Amjad wrote:
> > > When i use export from report manager to excel for some reason it gave us
> > > that error
> > > but one thing more i used open that report using visual studio on my friend
> > > computer and then preview the report and then select save as excel file . it
> > > didnt give me error but when i use report manager and then try to export to
> > > excel has that error
> > >
> > > Microsoft Excel File Repair Log
> > >
> > > Errors were detected in file C:\test.xls'
> > > The following is a list of repairs:
> > >
> > > Damage to the file was so extensive that repairs were not possible. Excel
> > > attempted to recover your formulas and values, but some data may have been
> > > lost or corrupted.
> >
> >

export to excel from a report

Hi, I would like to have a button on my report to export it to excel (instead of having to choose the format from the toolbar and then press "export").
Is there a way to do it? I know that there is a parameter that I can add to the url for this but i don't know exactly how to add it to the current url from my report).
Thanks
From http://www.developmentnow.com/g/115_0_0_0_0_0/sql-server-reporting-services.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.comsee my reply on "Nicknack" user query
Amarnath
"roy mm" wrote:
> Hi, I would like to have a button on my report to export it to excel (instead of having to choose the format from the toolbar and then press "export").
> Is there a way to do it? I know that there is a parameter that I can add to the url for this but i don't know exactly how to add it to the current url from my report).
> Thanks.
> From http://www.developmentnow.com/g/115_0_0_0_0_0/sql-server-reporting-services.htm
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
>

Export to Excel format

I am using SQL Server Reporting Services 2005.

In one of report i am calling sub report which independently renders in excel format without problem but when it is called in main report as SubReport in Data Table Cell in that cell its giving error message Subreports within table/matrix cells are ignored.

While rendering to PDF format it is working fine.I have problem only in excel format renderings..

The export to Excel dosn't support sub-reports. I re-worked my Excel Exporting reports to not include sub reports (which stinks! but that's the current limitation).

Tim

|||

I have the same problem.

I use SQL Reporting Service 2005. The report has a subreport embedded in a table.

when I exported this report into Excel, it started gving "Data Regions within table/matrix cells are ignored" error when is displayed in the section where Subreport is display. I need the information inside the subreport to be able exported into Excel file which is very important to me. What is alternative way to fix it?

Thanks in advance|||

Hi ,

To avoid sub -reports in sql reporting services 2005 follow the solution.

Have a main table.The row where sub report resides - replace it /drag a list control and place a table inside

Before:

<table>

<tr>

<td>your sub report</td>

</tr>

</table>

After:

<table>

<tr>

</tr>

</table>

Note : Nested table soln wrks this way only.

Filter the sub table as per your requirements / then grouping sorting . Then export to excel - everything wrks fine.

I hope this helps.

Regards,

shanthi

Export to Excel format

I am using SQL Server Reporting Services 2005.

While rendering to PDF format it is working fine.I have problem only in excel format renderings..

The export to Excel dosn't support sub-reports. I re-worked my Excel Exporting reports to not include sub reports (which stinks! but that's the current limitation).

Tim

|||

I have the same problem.

I use SQL Reporting Service 2005. The report has a subreport embedded in a table.

Thanks in advance|||

Hi ,

To avoid sub -reports in sql reporting services 2005 follow the solution.

Have a main table.The row where sub report resides - replace it /drag a list control and place a table inside

Before:

<table>

<tr>

<td>your sub report</td>

</tr>

</table>

After:

<table>

<tr>

</tr>

</table>

Note : Nested table soln wrks this way only.

Filter the sub table as per your requirements / then grouping sorting . Then export to excel - everything wrks fine.

I hope this helps.

Regards,

shanthi

export to excel file

I've created a dts package that exports data to an excel. The data exports okay, but I'd like to make a few changes on how the data is exported.

First, when the data exports to the excel file, it always creates a new excel sheet. How can I map the data to the existing sheet in the Excel file? I have an existing sheet named 'Sheet1'. I've deleted the other two sheets in the excel file, so there is only one sheet. When I created the destination table in the dts package for the data transformation task, I specified the name as 'Sheet1', but when it exports, it creates a new sheet named 'Sheet11'. I haven't been able to correct this.

Second, I'd like to either ammend data to the last row in the excel file, which I'd have to know the last record that was inserted from the SQL table. Or probably much easier, simply drop the existing sheet in the excel file and simply re-create and insert.

How can I do this?

Thanks,
-D-I figured it out...please disregard.

Export to Excel fails - ASPNET_WP.EXE consumes 60% RAM

I'm trying to export a report to Excel that contains 60,000 rows (but not
more than Excels 65,000 limit) and I get an "internal server error".
When I check the event log on the server it states that aspnet_wp.exe
terminated the report process because it had consumed more than 60% of the
servers availible RAM (1Gb total).
PDF and CSV work fine. Does anyone know anything about this'
--
Cheers
NickExporting to Excel is quite intensive on resources. The problem is that MS
is trying for very high fidelity on what the data looks like. For instance
if you have drill down it creates a spreadsheet with drilldown. For that
amount of data I suggest that you use CSV in ASCII format (the default is
Unicode). Excel doesn't recognize Unicode CSV and puts it all in one column.
With ASCII format Excel properly puts them in the correct columns. Another
tip, for your table in the report, click on each field of the detail and
make sure it has the name that you want on Export. The CSV export uses this
name. To get CSV in ASCII you need to use a jump to URL and include ASCII in
the deviceinfo (or something like that, doing this from memory from home).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Nick Prudhoe" <NickPrudhoe@.discussions.microsoft.com> wrote in message
news:3F7F032F-9416-462B-89BC-F6C90E64FA5A@.microsoft.com...
> I'm trying to export a report to Excel that contains 60,000 rows (but not
> more than Excels 65,000 limit) and I get an "internal server error".
> When I check the event log on the server it states that aspnet_wp.exe
> terminated the report process because it had consumed more than 60% of the
> servers availible RAM (1Gb total).
> PDF and CSV work fine. Does anyone know anything about this'
> --
> Cheers
> Nick|||Thanks. I have already managed to get the same report to export to CSV. I'm
trying to prove reporting services out before my company goes down that
track. The performance on exports to Excel is disapointing, i would have
hoped it was better than PDF as it's an MS technology.
--
Cheers
Nick
"Bruce L-C [MVP]" wrote:
> Exporting to Excel is quite intensive on resources. The problem is that MS
> is trying for very high fidelity on what the data looks like. For instance
> if you have drill down it creates a spreadsheet with drilldown. For that
> amount of data I suggest that you use CSV in ASCII format (the default is
> Unicode). Excel doesn't recognize Unicode CSV and puts it all in one column.
> With ASCII format Excel properly puts them in the correct columns. Another
> tip, for your table in the report, click on each field of the detail and
> make sure it has the name that you want on Export. The CSV export uses this
> name. To get CSV in ASCII you need to use a jump to URL and include ASCII in
> the deviceinfo (or something like that, doing this from memory from home).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Nick Prudhoe" <NickPrudhoe@.discussions.microsoft.com> wrote in message
> news:3F7F032F-9416-462B-89BC-F6C90E64FA5A@.microsoft.com...
> > I'm trying to export a report to Excel that contains 60,000 rows (but not
> > more than Excels 65,000 limit) and I get an "internal server error".
> >
> > When I check the event log on the server it states that aspnet_wp.exe
> > terminated the report process because it had consumed more than 60% of the
> > servers availible RAM (1Gb total).
> >
> > PDF and CSV work fine. Does anyone know anything about this'
> > --
> > Cheers
> > Nick
>
>|||Yeah...one would think...although I have seen a significant performance
improvement in service pack 2.
Nick Prudhoe wrote:
> Thanks. I have already managed to get the same report to export to CSV. I'm
> trying to prove reporting services out before my company goes down that
> track. The performance on exports to Excel is disapointing, i would have
> hoped it was better than PDF as it's an MS technology.
>

Export to Excel failed with System.OutOfMemoryException

Server: SQL Server 2000 Ent running on Win2k AS, Ent Edition of Reporting
Services + SP1
my workstation: Win2k SP4, Microsoft Development Environment v7.1.3088,
Reporting Services Ent Ed + SP1.
I am trying to export 55,804 rows to Excel. The table that I am exporting
from has 11 columns.
-- Columns within >results< -- DataType Length
--- -- --
Source varchar 2
ClaimNumber varchar 17
MarketLoc varchar 7
Description varchar 50
SomeDate datetime 8
DetailNo smallint 2
ChargeCode varchar 1
UnitCount smallint 2
ChargedDollars decimal 5
AllowedDollars decimal 5
NetPaidDollars decimal 5
Because I need to dump this data for 17 different market locations ranging
in rowcounts of 600 rows to 56,000 rows I figured that I would just create a
report within Reporting Services and query the results table (228,825 rows)
table for each of the 17 market locations. I would export each market to an
Excel file and then I would copy/paste the worksheets into one file that I
can send to the end user. This would be easier than selecting the
information within Query Analyzer, saving to a file, importing each file,
formatting each column and repeating the process for each of the 17 groups
of data.
I started out with a small data set (1500 rows) as a proof of concept so
that I knew the process would work. When I had the report formatted
correctly I successfully exported the data to Excel. Then I moved on to one
of the larger groups (55,804 rows). This is where I had the problems.
I previewed the report within Visual Studio. Total page count 1241. The
rdl.data file is 12MB. I clicked on the disk icon on the toolbar and chose
to export the report to Excel. I have 768MB of RAM in my machine and the
memory usage continued to rise until it reached 1GB. This process took over
20 minutes. At the end of it all I received a dialog box indicating a
System.OutOfMemoryException was thrown. What would happen if I tried
running this on the server? I am guessing that it would consume lots of CPU
cycles and eat up lots of memory. Would it finish, or would it fail? I am
afraid to try :)
Why is the .rdl.data only 12MB yet over 1GB was consumed while converting to
Excel? When I save the results to a [text] file within Query Analyzer the
file is 12MB. I could import into Excel, but then I have to import x files
and format y columns x times.
This should be fairly easy to repro. Does anyone from Microsoft want to
take a look at it? Does anyone else have any ideas?
--
KeithKeith,
The only recommendation I have at this time is to increase the RAM on the
machine you are using to export to excel. I do not have a specific
recommendation, but I would suggest a minimum of 1GB of RAM. The SQL Server
2000 Reporting Services team is looking at addressing this issue in upcoming
service packs and releases.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:eo8Ko5qXEHA.2868@.TK2MSFTNGP09.phx.gbl...
> Server: SQL Server 2000 Ent running on Win2k AS, Ent Edition of Reporting
> Services + SP1
> my workstation: Win2k SP4, Microsoft Development Environment v7.1.3088,
> Reporting Services Ent Ed + SP1.
> I am trying to export 55,804 rows to Excel. The table that I am exporting
> from has 11 columns.
> -- Columns within >results< -- DataType Length
> --- -- --
> Source varchar 2
> ClaimNumber varchar 17
> MarketLoc varchar 7
> Description varchar 50
> SomeDate datetime 8
> DetailNo smallint 2
> ChargeCode varchar 1
> UnitCount smallint 2
> ChargedDollars decimal 5
> AllowedDollars decimal 5
> NetPaidDollars decimal 5
> Because I need to dump this data for 17 different market locations ranging
> in rowcounts of 600 rows to 56,000 rows I figured that I would just create
a
> report within Reporting Services and query the results table (228,825
rows)
> table for each of the 17 market locations. I would export each market to
an
> Excel file and then I would copy/paste the worksheets into one file that I
> can send to the end user. This would be easier than selecting the
> information within Query Analyzer, saving to a file, importing each file,
> formatting each column and repeating the process for each of the 17 groups
> of data.
> I started out with a small data set (1500 rows) as a proof of concept so
> that I knew the process would work. When I had the report formatted
> correctly I successfully exported the data to Excel. Then I moved on to
one
> of the larger groups (55,804 rows). This is where I had the problems.
> I previewed the report within Visual Studio. Total page count 1241. The
> rdl.data file is 12MB. I clicked on the disk icon on the toolbar and
chose
> to export the report to Excel. I have 768MB of RAM in my machine and the
> memory usage continued to rise until it reached 1GB. This process took
over
> 20 minutes. At the end of it all I received a dialog box indicating a
> System.OutOfMemoryException was thrown. What would happen if I tried
> running this on the server? I am guessing that it would consume lots of
CPU
> cycles and eat up lots of memory. Would it finish, or would it fail? I
am
> afraid to try :)
> Why is the .rdl.data only 12MB yet over 1GB was consumed while converting
to
> Excel? When I save the results to a [text] file within Query Analyzer the
> file is 12MB. I could import into Excel, but then I have to import x
files
> and format y columns x times.
> This should be fairly easy to repro. Does anyone from Microsoft want to
> take a look at it? Does anyone else have any ideas?
> --
> Keith
>|||Bruce, Thanks for your reply. It is unfortunate that 768MB is not enough
memory to export ~12MB of data to Excel. I am glad that Microsoft enhanced
the versions of Excel that are supported with RS SP1. Now I guess I will
have to wait for SP2 (or SQL Server 2005) for memory optimization.
In the end I ended up getting the data into Excel via the "Get External Data
| from a database query" menu. Yeah, I had to do it 17 times, but it
worked. That method saved me the pain of having to perform a "data | text
to columns" and format each column..
Keep up the good work!
--
Keith
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message
news:OmRdOCsXEHA.3664@.TK2MSFTNGP12.phx.gbl...
> Keith,
> The only recommendation I have at this time is to increase the RAM on the
> machine you are using to export to excel. I do not have a specific
> recommendation, but I would suggest a minimum of 1GB of RAM. The SQL
Server
> 2000 Reporting Services team is looking at addressing this issue in
upcoming
> service packs and releases.
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
> news:eo8Ko5qXEHA.2868@.TK2MSFTNGP09.phx.gbl...
> > Server: SQL Server 2000 Ent running on Win2k AS, Ent Edition of
Reporting
> > Services + SP1
> > my workstation: Win2k SP4, Microsoft Development Environment v7.1.3088,
> > Reporting Services Ent Ed + SP1.
> >
> > I am trying to export 55,804 rows to Excel. The table that I am
exporting
> > from has 11 columns.
> >
> > -- Columns within >results< -- DataType Length
> > --- -- --
> > Source varchar 2
> > ClaimNumber varchar 17
> > MarketLoc varchar 7
> > Description varchar 50
> > SomeDate datetime 8
> > DetailNo smallint 2
> > ChargeCode varchar 1
> > UnitCount smallint 2
> > ChargedDollars decimal 5
> > AllowedDollars decimal 5
> > NetPaidDollars decimal 5
> >
> > Because I need to dump this data for 17 different market locations
ranging
> > in rowcounts of 600 rows to 56,000 rows I figured that I would just
create
> a
> > report within Reporting Services and query the results table (228,825
> rows)
> > table for each of the 17 market locations. I would export each market
to
> an
> > Excel file and then I would copy/paste the worksheets into one file that
I
> > can send to the end user. This would be easier than selecting the
> > information within Query Analyzer, saving to a file, importing each
file,
> > formatting each column and repeating the process for each of the 17
groups
> > of data.
> >
> > I started out with a small data set (1500 rows) as a proof of concept so
> > that I knew the process would work. When I had the report formatted
> > correctly I successfully exported the data to Excel. Then I moved on to
> one
> > of the larger groups (55,804 rows). This is where I had the problems.
> >
> > I previewed the report within Visual Studio. Total page count 1241.
The
> > rdl.data file is 12MB. I clicked on the disk icon on the toolbar and
> chose
> > to export the report to Excel. I have 768MB of RAM in my machine and
the
> > memory usage continued to rise until it reached 1GB. This process took
> over
> > 20 minutes. At the end of it all I received a dialog box indicating a
> > System.OutOfMemoryException was thrown. What would happen if I tried
> > running this on the server? I am guessing that it would consume lots of
> CPU
> > cycles and eat up lots of memory. Would it finish, or would it fail? I
> am
> > afraid to try :)
> >
> > Why is the .rdl.data only 12MB yet over 1GB was consumed while
converting
> to
> > Excel? When I save the results to a [text] file within Query Analyzer
the
> > file is 12MB. I could import into Excel, but then I have to import x
> files
> > and format y columns x times.
> >
> > This should be fairly easy to repro. Does anyone from Microsoft want to
> > take a look at it? Does anyone else have any ideas?
> >
> > --
> > Keith
> >
> >
>

Export to Excel failed with ReportItems and sub report

Hi,

I have two RDL files, one is main.rdl, the other one is sub.rdl.

In the body of main.rdl, I threw in a subreport that links to sub.rdl. Follow by the subreport is a table, in which has a textbox called mytitle. In the page footer, I added one text box that references to mytitle by using ReportItems!mytitle.Value.

When this report rendered in HTML or PDF format, it worked fine. However, when exporting to excel format, it failed. I figured it is because there isn't a ReportItem in the subreport called mytitle. I tried adding a dummy textbox into the subreport and called it mytitle, but again, no luck.

Did anyone ever encounter the same problem? Is there a work around way?

Thanks,

How did the export fail? Did the report not export at all, or it was part of the report that didn't work? What error did you get? The excel renderer doesn't support nested tables/matrics. Did you have some complex in the subreport?|||

I've done more testing on the problem. I didn't use nested tables/matrics in main and sub reports. In my sub report, it has two tables, not nested, one follows the other.

The report was not exporting at all. It gave me an error when I tried to export to Excel in VS.NET 2005. The error message was:

An error occurred during local report processing.

An error occurred during rendering of the report.

An error occurred during rendering of the report

An unexpected error occurred in Report Processing.

The expression referenced a non-existing reportitem in the reportitems collection.

|||This sounds like a problem in our code. Can you attach your RDL please?|||

RDL for the main report

|||

RDL for sub report

<?xml version="1.0" encoding="utf-8"?>
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<DataSources>
<DataSource Name="DS">
<DataSourceReference>DS</DataSourceReference>
<rd:DataSourceID>fe1336f9-bea0-4334-8dca-de54f755ec93</rd:DataSourceID>
</DataSource>
</DataSources>
<BottomMargin>1in</BottomMargin>
<RightMargin>1in</RightMargin>
<rd:DrawGrid>true</rd:DrawGrid>
<InteractiveWidth>8.5in</InteractiveWidth>
<rd:SnapToGrid>true</rd:SnapToGrid>
<Body>
<ReportItems>
<Table Name="table2">
<Footer>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="textbox9">
<rd:DefaultName>textbox9</rd:DefaultName>
<ZIndex>5</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox10">
<rd:DefaultName>textbox10</rd:DefaultName>
<ZIndex>4</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox11">
<rd:DefaultName>textbox11</rd:DefaultName>
<ZIndex>3</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.25in</Height>
</TableRow>
</TableRows>
</Footer>
<DataSetName>DS2</DataSetName>
<Top>1.125in</Top>
<ZIndex>3</ZIndex>
<Details>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="ID_1">
<rd:DefaultName>ID_1</rd:DefaultName>
<ZIndex>2</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>=Fields!ID.Value</Value>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox7">
<rd:DefaultName>textbox7</rd:DefaultName>
<ZIndex>1</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox8">
<rd:DefaultName>textbox8</rd:DefaultName>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.25in</Height>
</TableRow>
</TableRows>
</Details>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
</Style>
<Header>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="textbox3">
<rd:DefaultName>textbox3</rd:DefaultName>
<ZIndex>8</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<BackgroundColor>Turquoise</BackgroundColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>Second Table</Value>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox4">
<rd:DefaultName>textbox4</rd:DefaultName>
<ZIndex>7</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox5">
<rd:DefaultName>textbox5</rd:DefaultName>
<ZIndex>6</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.25in</Height>
</TableRow>
</TableRows>
</Header>
<TableColumns>
<TableColumn>
<Width>1.66667in</Width>
</TableColumn>
<TableColumn>
<Width>1.66667in</Width>
</TableColumn>
<TableColumn>
<Width>1.66667in</Width>
</TableColumn>
</TableColumns>
<Height>0.75in</Height>
</Table>
<Textbox Name="ForFooter">
<Top>2.25in</Top>
<ZIndex>2</ZIndex>
<Width>2.75in</Width>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Height>0.25in</Height>
<Value>Dummy TextBox for Footer in MainReport</Value>
</Textbox>
<Textbox Name="textbox1">
<rd:DefaultName>textbox1</rd:DefaultName>
<ZIndex>1</ZIndex>
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>20pt</FontSize>
<Color>SteelBlue</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Height>0.36in</Height>
<Value>SubReport</Value>
</Textbox>
<Table Name="table1">
<DataSetName>DS1</DataSetName>
<Top>0.5in</Top>
<Width>2in</Width>
<Details>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="ID">
<rd:DefaultName>ID</rd:DefaultName>
<ZIndex>1</ZIndex>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>=Fields!ID.Value</Value>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox12">
<rd:DefaultName>textbox12</rd:DefaultName>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.21in</Height>
</TableRow>
</TableRows>
</Details>
<Header>
<TableRows>
<TableRow>
<TableCells>
<TableCell>
<ReportItems>
<Textbox Name="textbox2">
<rd:DefaultName>textbox2</rd:DefaultName>
<ZIndex>3</ZIndex>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>11pt</FontSize>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BackgroundColor>SteelBlue</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value>First table</Value>
</Textbox>
</ReportItems>
</TableCell>
<TableCell>
<ReportItems>
<Textbox Name="textbox6">
<rd:DefaultName>textbox6</rd:DefaultName>
<ZIndex>2</ZIndex>
<Style>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<FontFamily>Tahoma</FontFamily>
<FontWeight>700</FontWeight>
<FontSize>11pt</FontSize>
<BorderColor>
<Default>LightGrey</Default>
</BorderColor>
<BackgroundColor>SteelBlue</BackgroundColor>
<Color>White</Color>
<PaddingRight>2pt</PaddingRight>
<PaddingTop>2pt</PaddingTop>
</Style>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</TableCell>
</TableCells>
<Height>0.22in</Height>
</TableRow>
</TableRows>
<RepeatOnNewPage>true</RepeatOnNewPage>
</Header>
<TableColumns>
<TableColumn>
<Width>1in</Width>
</TableColumn>
<TableColumn>
<Width>1in</Width>
</TableColumn>
</TableColumns>
<Height>0.43in</Height>
</Table>
</ReportItems>
<Height>4.79in</Height>
</Body>
<rd:ReportID>d7980735-ccd4-4952-b9e3-849d60c1bc55</rd:ReportID>
<LeftMargin>1in</LeftMargin>
<DataSets>
<DataSet Name="DS1">
<Query>
<rd:UseGenericDesigner>true</rd:UseGenericDesigner>
<CommandText>Select 'Value in Sub Report' AS ID</CommandText>
<DataSourceName>DS</DataSourceName>
</Query>
<Fields>
<Field Name="ID">
<rd:TypeName>System.String</rd:TypeName>
<DataField>ID</DataField>
</Field>
</Fields>
</DataSet>
<DataSet Name="DS2">
<Query>
<rd:UseGenericDesigner>true</rd:UseGenericDesigner>
<CommandText>SELECT 'Second Table in SubReport' AS ID</CommandText>
<DataSourceName>DS</DataSourceName>
</Query>
<Fields>
<Field Name="ID">
<rd:TypeName>System.String</rd:TypeName>
<DataField>ID</DataField>
</Field>
</Fields>
</DataSet>
</DataSets>
<Width>5in</Width>
<InteractiveHeight>11in</InteractiveHeight>
<Language>en-US</Language>
<TopMargin>1in</TopMargin>
</Report>

|||Is this going to be resolved in the next service pack?|||I've filed a bug in our internal bug tracking database. We'll consider it for the next service pack or a future release. Thanks for reporting it.|||We have actually fixed this issue in SQL Server 2005 SP1. Please try it and let us know if it still doesn't work for you.|||

In Portuguese: Excelente

In Inglish: It's Very Good...

Thiago Cruz

thiago.cruz@.dotnetraptors.com.br

|||This was working without SP1 and is now broken after installing SP1.|||

i have vs studio 2k5 sp1 installed and i am getting this error. I have office 2003 installed. Is there still a bug ticket out for this? For now what I do is wait until the report is loaded then delete Excel from the dropdown list so it can't be accessed ( so the user can't generate this error, but it would nice to be working.)

Here is the code to remove Excel from the drop down list ...

Code Snippet

Dim dropExport As DropDownList = ReportViewer1.Controls(1).Controls(5).Controls(0)

dropExport.SelectedValue = "EXCEL"

dropExport.Items.RemoveAt(dropExport.SelectedIndex)

And here is the stack trace of the error when I click Export while Excel is selected:

Code Snippet

[Exception: The expression referenced a non-existing reportitem in the reportitems collection.]

[Exception: An unexpected error occurred in Report Processing.]

[Exception: An error occurred during rendering of the report.]

[Exception: An error occurred during rendering of the report.]
Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension) +553
Microsoft.Reporting.WebForms.ServerReport.InternalRender(Boolean isAbortable, String format, String deviceInfo, NameValueCollection urlAccessParameters, Stream reportStream, String& mimeType, String& fileNameExtension) +941
Microsoft.Reporting.WebForms.ServerReport.Render(String format, String deviceInfo, NameValueCollection urlAccessParameters, String& mimeType, String& fileNameExtension) +97
Microsoft.Reporting.WebForms.ServerReportControlSource.RenderReport(String format, String deviceInfo, NameValueCollection additionalParams, String& mimeType, String& fileExtension) +126
Microsoft.Reporting.WebForms.ExportOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response) +153
Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context) +202
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

|||

I have exactly the same error here. I have a list on the report body(to avoid the excel sub-reports rendering problem, I have to use list instead of table). There is a textbox and some other sub-reports on the list. A textbox in the header reference the list textbox.

The report looks ok for the screen view, but when I try the "Excel" export, I got the "The expression referenced a non-existing reportitem in the reportitems collection. " error. If I remove all sub-reports, it works fine.

My SQL server installed SP2. Below is the version message for the sql server [ Microsoft SQL Server 2005 - 9.00.1406.00 (Intel X86) Mar 3 2007 18:40:02 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 2) ]. Appreciate any help!

(I'm using VS2005 with SP1, and reportviewer control with asp.net)

|||

Could any body give any help?

Thanks!

Export to Excel failed with ReportItems and sub report

Hi,

I have two RDL files, one is main.rdl, the other one is sub.rdl.

Did anyone ever encounter the same problem? Is there a work around way?

Thanks,

I've done more testing on the problem. I didn't use nested tables/matrics in main and sub reports. In my sub report, it has two tables, not nested, one follows the other.

The report was not exporting at all. It gave me an error when I tried to export to Excel in VS.NET 2005. The error message was:

An error occurred during local report processing.

An error occurred during rendering of the report.

An error occurred during rendering of the report

An unexpected error occurred in Report Processing.

The expression referenced a non-existing reportitem in the reportitems collection.

|||This sounds like a problem in our code. Can you attach your RDL please?|||

RDL for the main report

|||

RDL for sub report

In Portuguese: Excelente

In Inglish: It's Very Good...

Thiago Cruz

thiago.cruz@.dotnetraptors.com.br

|||This was working without SP1 and is now broken after installing SP1.|||

Here is the code to remove Excel from the drop down list ...

Code Snippet

Dim dropExport As DropDownList = ReportViewer1.Controls(1).Controls(5).Controls(0)

dropExport.SelectedValue = "EXCEL"

dropExport.Items.RemoveAt(dropExport.SelectedIndex)

And here is the stack trace of the error when I click Export while Excel is selected:

Code Snippet

[Exception: The expression referenced a non-existing reportitem in the reportitems collection.]

[Exception: An unexpected error occurred in Report Processing.]

[Exception: An error occurred during rendering of the report.]

|||

(I'm using VS2005 with SP1, and reportviewer control with asp.net)

|||

Could any body give any help?

Thanks!

Sunday, February 26, 2012

Export to Excel Problem

Export to Excel Problem

Export To Excel problem

export to excel percentage problem

Export to excel number formatting problem

Export to Excel -multiple sheets

Export to Excel -multiple sheets

Export to Excel -multiple sheets

Export to Excel missing last row

Export to Excel madness

Export to Excel Link - Inactive -Critical - Need Help

Export to Excel Legal Landscape

export to excel issues

Export to excel issue

Export to Excel in MS Access

export to excel has merged cell problem

Export To Excel Gives Me Gray Cells

Export To Excel Funny Result post Sp1

Export to Excel Functionality (SQL RS 2005)?

Export to Excel from SQL Server 2000

Export to excel from report manager problem

export to excel from a report

Export to Excel format

Export to Excel format

export to excel file

Export to Excel fails - ASPNET_WP.EXE consumes 60% RAM

Export to Excel failed with System.OutOfMemoryException

Export to Excel failed with ReportItems and sub report

Export to Excel failed with ReportItems and sub report

Export Report to File

Blog Archive

About Me