Export to excel problem

Hi,

I have a tabular report that has a toggle(collapsible item) in the details area. The toggle works fine in the report designer but when I export it to excel, the toggle is not exported. Are there some properties that I missed configuring?

Thanks!

Do you have other table rows between details and the row with the toggle? If this is the case, we cannot generate the outlines in Excel since Excel requires the rows to be consecutive.

Thank you,

Nico

|||

We had no problem when we use Reporting Services Standard edition. But after we installed Reporting Service SP2, we got the same problem as you. Unfortunately, I don't have solution yet.

Do you have Reporting Services SP2 installed?

Please let me know.

Alison

|||Did you set the visibility of the table to some expression? If so, just set to visible or hidden, then the toggle will be exported in Excel.

Export to excel problem

Hi,

WHen i export a report(which i dynamically create) to excel it spews the following :

MIME-Version: 1.0

X-Document-Type: Workbook

Content-Type: multipart/related;boundary="-=_NextPart_01C35DB7.4B204430"

This is a multi-part message in MIME format.

=_NextPart_01C35DB7.4B204430

Content-Type: text/html;

charset="utf-8"

Content-Transfer-Encoding: base64

Content-Location: file:///c:/Report.htm

77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zPSJodHRwOi8vIHd3dy53My5vcmcvVFIvUkVDLWh0bWw0MCI+CjxoZWFkPgo8bWV0YSBuYW1lPSJFeGNlbCBXb3JrYm9vayBGcmFtZXNldCI+CjxtZXRhIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+Cjx4bWw+PG86RG9jdW1lbnRQcm9wZXJ0aWVzPjxvOkNyZWF0ZWQ+RnJpZGF5LCAxMiBNYXkgMjAwNiAxNTowOToxNDwvbzpDcmVhdGVkPgo8bzpMYXN0U2F2ZWQ+RnJpZGF5LCAxMiBNYXkgMjAwNiAxNTowOToxNDwvbzpMYXN0U2F2ZWQ+CjwvbzpEb2N1bWVudFByb3BlcnRpZXM+PC94bWw+PGxpbmsgaWQ9InNoTGluayIgaHJlZj0iU2hlZXQxLmh0bSI+PHhtbD48eDpFeGNlbFdvcmtib29rPjx4OkV4Y2VsV29ya3NoZWV0cz48eDpFeGNlbFdvcmtzaGVldD48eDpOYW1lPlJlcG9ydDwveDpOYW1lPjx4OldvcmtzaGVldFNvdXJjZSBIUmVmPSJTaGVldDEuaHRtIi8+PHg6V29ya3NoZWV0T3B0aW9ucz48eDpOb1N1bW1hcnlSb3dzQmVsb3dEZXRhaWwvPjx4Ok5vU3VtbWFyeUNvbHVtbnNSaWdodERldGFpbC8+PHg6RG9Ob3REaXNwbGF5R3JpZGxpbmVzLz48eDpQcmludD48eDpWYWxpZFByaW50ZXJJbmZvLz48eDpQYXBlclNp

=_NextPart_01C35DB7.4B204430

Content-Type: text/html

Content-Transfer-Encoding: base64

Content-Location: file:///c:/Sheet1.htm

Any ideas on how to resolve this?

I am experiencing the same exact problem on two machines. Did you ever find an answer?

|||

Can anyone help us? I am still looking for a solution.

Thanks. -Nittany92

|||

What version and service pack level of RS are you using? Can you please explain exactly what steps you are taking to export the report?

Thanks,
Chris

|||

I did finally find out that this issue was fixed in SQL Reporting Services SP1. Our reporting server was using SP1 but I was only given the original release to install on my PC. I have since applied SQL Reporting Services SP2 to my PC and I am now able to export to an Excel 2000 file successfully.

See the following info...

http://download.microsoft.com/download/5/1/3/513534ae-a0e7-44e6-9a04-ba3c549a5f5f/sp2Readme_EN.htm

4.2.8 Excel Rendering Extension

New in SP1. Significant improvements have been made to the Excel rendering extension. The output format produced by the rendering extension has changed. Improvements include the following: Rendered reports can now be opened in Excel 97 and later. Previously, the file format was MIME Encapsulation of Aggregate HTML (MHTML), which could only be opened in Excel 2002 and later. The format for rendered reports is now Binary Interchange File Format (BIFF), which can be opened in Excel 97 and later.

Export to excel problem

Hi,

WHen i export a report(which i dynamically create) to excel it spews the following :

MIME-Version: 1.0

X-Document-Type: Workbook

Content-Type: multipart/related;boundary="-=_NextPart_01C35DB7.4B204430"

This is a multi-part message in MIME format.

=_NextPart_01C35DB7.4B204430

Content-Type: text/html;

charset="utf-8"

Content-Transfer-Encoding: base64

Content-Location: file:///c:/Report.htm

77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zPSJodHRwOi8vIHd3dy53My5vcmcvVFIvUkVDLWh0bWw0MCI+CjxoZWFkPgo8bWV0YSBuYW1lPSJFeGNlbCBXb3JrYm9vayBGcmFtZXNldCI+CjxtZXRhIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+Cjx4bWw+PG86RG9jdW1lbnRQcm9wZXJ0aWVzPjxvOkNyZWF0ZWQ+RnJpZGF5LCAxMiBNYXkgMjAwNiAxNTowOToxNDwvbzpDcmVhdGVkPgo8bzpMYXN0U2F2ZWQ+RnJpZGF5LCAxMiBNYXkgMjAwNiAxNTowOToxNDwvbzpMYXN0U2F2ZWQ+CjwvbzpEb2N1bWVudFByb3BlcnRpZXM+PC94bWw+PGxpbmsgaWQ9InNoTGluayIgaHJlZj0iU2hlZXQxLmh0bSI+PHhtbD48eDpFeGNlbFdvcmtib29rPjx4OkV4Y2VsV29ya3NoZWV0cz48eDpFeGNlbFdvcmtzaGVldD48eDpOYW1lPlJlcG9ydDwveDpOYW1lPjx4OldvcmtzaGVldFNvdXJjZSBIUmVmPSJTaGVldDEuaHRtIi8+PHg6V29ya3NoZWV0T3B0aW9ucz48eDpOb1N1bW1hcnlSb3dzQmVsb3dEZXRhaWwvPjx4Ok5vU3VtbWFyeUNvbHVtbnNSaWdodERldGFpbC8+PHg6RG9Ob3REaXNwbGF5R3JpZGxpbmVzLz48eDpQcmludD48eDpWYWxpZFByaW50ZXJJbmZvLz48eDpQYXBlclNp

=_NextPart_01C35DB7.4B204430

Content-Type: text/html

Content-Transfer-Encoding: base64

Content-Location: file:///c:/Sheet1.htm

Any ideas on how to resolve this?

I am experiencing the same exact problem on two machines. Did you ever find an answer?

|||

Can anyone help us? I am still looking for a solution.

Thanks. -Nittany92

|||

What version and service pack level of RS are you using? Can you please explain exactly what steps you are taking to export the report?

Thanks,
Chris

|||

I did finally find out that this issue was fixed in SQL Reporting Services SP1. Our reporting server was using SP1 but I was only given the original release to install on my PC. I have since applied SQL Reporting Services SP2 to my PC and I am now able to export to an Excel 2000 file successfully.

See the following info...

http://download.microsoft.com/download/5/1/3/513534ae-a0e7-44e6-9a04-ba3c549a5f5f/sp2Readme_EN.htm

4.2.8 Excel Rendering Extension

New in SP1. Significant improvements have been made to the Excel rendering extension. The output format produced by the rendering extension has changed. Improvements include the following:

Rendered reports can now be opened in Excel 97 and later. Previously, the file format was MIME Encapsulation of Aggregate HTML (MHTML), which could only be opened in Excel 2002 and later. The format for rendered reports is now Binary Interchange File Format (BIFF), which can be opened in Excel 97 and later.

Export to excel problem

Hi,

I have a tabular report that has a toggle(collapsible item) in the details area. The toggle works fine in the report designer but when I export it to excel, the toggle is not exported. Are there some properties that I missed configuring?

Thanks!

Do you have other table rows between details and the row with the toggle? If this is the case, we cannot generate the outlines in Excel since Excel requires the rows to be consecutive.

Thank you,

Nico

|||

We had no problem when we use Reporting Services Standard edition. But after we installed Reporting Service SP2, we got the same problem as you. Unfortunately, I don't have solution yet.

Do you have Reporting Services SP2 installed?

Please let me know.

Alison

|||Did you set the visibility of the table to some expression? If so, just set to visible or hidden, then the toggle will be exported in Excel.

Export to excel problem

Hi,

WHen i export a report(which i dynamically create) to excel it spews the following :

MIME-Version: 1.0

X-Document-Type: Workbook

Content-Type: multipart/related;boundary="-=_NextPart_01C35DB7.4B204430"

This is a multi-part message in MIME format.

=_NextPart_01C35DB7.4B204430

Content-Type: text/html;

charset="utf-8"

Content-Transfer-Encoding: base64

Content-Location: file:///c:/Report.htm

77u/PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVybjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zPSJodHRwOi8vIHd3dy53My5vcmcvVFIvUkVDLWh0bWw0MCI+CjxoZWFkPgo8bWV0YSBuYW1lPSJFeGNlbCBXb3JrYm9vayBGcmFtZXNldCI+CjxtZXRhIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+Cjx4bWw+PG86RG9jdW1lbnRQcm9wZXJ0aWVzPjxvOkNyZWF0ZWQ+RnJpZGF5LCAxMiBNYXkgMjAwNiAxNTowOToxNDwvbzpDcmVhdGVkPgo8bzpMYXN0U2F2ZWQ+RnJpZGF5LCAxMiBNYXkgMjAwNiAxNTowOToxNDwvbzpMYXN0U2F2ZWQ+CjwvbzpEb2N1bWVudFByb3BlcnRpZXM+PC94bWw+PGxpbmsgaWQ9InNoTGluayIgaHJlZj0iU2hlZXQxLmh0bSI+PHhtbD48eDpFeGNlbFdvcmtib29rPjx4OkV4Y2VsV29ya3NoZWV0cz48eDpFeGNlbFdvcmtzaGVldD48eDpOYW1lPlJlcG9ydDwveDpOYW1lPjx4OldvcmtzaGVldFNvdXJjZSBIUmVmPSJTaGVldDEuaHRtIi8+PHg6V29ya3NoZWV0T3B0aW9ucz48eDpOb1N1bW1hcnlSb3dzQmVsb3dEZXRhaWwvPjx4Ok5vU3VtbWFyeUNvbHVtbnNSaWdodERldGFpbC8+PHg6RG9Ob3REaXNwbGF5R3JpZGxpbmVzLz48eDpQcmludD48eDpWYWxpZFByaW50ZXJJbmZvLz48eDpQYXBlclNp

=_NextPart_01C35DB7.4B204430

Content-Type: text/html

Content-Transfer-Encoding: base64

Content-Location: file:///c:/Sheet1.htm

Any ideas on how to resolve this?

I am experiencing the same exact problem on two machines. Did you ever find an answer?

|||

Can anyone help us? I am still looking for a solution.

Thanks. -Nittany92

|||

What version and service pack level of RS are you using? Can you please explain exactly what steps you are taking to export the report?

Thanks,
Chris

|||

I did finally find out that this issue was fixed in SQL Reporting Services SP1. Our reporting server was using SP1 but I was only given the original release to install on my PC. I have since applied SQL Reporting Services SP2 to my PC and I am now able to export to an Excel 2000 file successfully.

See the following info...

http://download.microsoft.com/download/5/1/3/513534ae-a0e7-44e6-9a04-ba3c549a5f5f/sp2Readme_EN.htm

4.2.8 Excel Rendering Extension

New in SP1. Significant improvements have been made to the Excel rendering extension. The output format produced by the rendering extension has changed. Improvements include the following: Rendered reports can now be opened in Excel 97 and later. Previously, the file format was MIME Encapsulation of Aggregate HTML (MHTML), which could only be opened in Excel 2002 and later. The format for rendered reports is now Binary Interchange File Format (BIFF), which can be opened in Excel 97 and later.

Export to excel problem

Hi,

I have a tabular report that has a toggle(collapsible item) in the details area. The toggle works fine in the report designer but when I export it to excel, the toggle is not exported. Are there some properties that I missed configuring?

Thanks!

Do you have other table rows between details and the row with the toggle? If this is the case, we cannot generate the outlines in Excel since Excel requires the rows to be consecutive.

Thank you,

Nico

|||

We had no problem when we use Reporting Services Standard edition. But after we installed Reporting Service SP2, we got the same problem as you. Unfortunately, I don't have solution yet.

Do you have Reporting Services SP2 installed?

Please let me know.

Alison

|||Did you set the visibility of the table to some expression? If so, just set to visible or hidden, then the toggle will be exported in Excel.

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
>