Okay, I'll try my best to explain this....
I have a table on my report. Above the header for 5 of my columns, I need
to place a cell that spans all those columns. It looks like this:
--
| h |
--
| h | h | h | h | h |
--
| d | d | d | d | d |
--
h = header row
d = detail row
so, to do this I took the header cell for the left most column and merged it
with the
4 other header cells. Then I put a rectangle into that cell, and drew a
line through the middle to create the two level effect in the single header
cell. Then, where each 'h' is in the above diagram, I put a text box with
some text in it that serves as a label. So, basically all 5 of my detail
columns have their own individual header, as well as a header that applies to
all of them.
When I run the report, and export it to PDF, everything looks great. When I
export to excel, I get a strange effect. SRS seems to want to put the cell
for the textbox in the bottom right most 'cell' in the header in a row below
the other 4 in the second header 'row'.. So, it looks like this in Excel:
--
| h |
--
| h | h | h | h | |
--
| h |
| --|
| d | d | d | d | d |
--
h = header row
d = detail row
Anybody have any idea what's going on here? If I remove the 5th text box in
the header (the one that's causing the problem), excel formats fine.
It would be nice if I could merge cells across rows as well as columns,
because that would make this problem trivial.
Any help is greatly appreciated.
Jeff
JeffJeff,
Have you tried inserting a second table header row above the original table
header row? Then do the merging on the inserted header row. I just did this
on a report at my work. Doing so gave me this effect:
| H1 |
|H1|H2|H3|H4|
|D1|D2|D3|D4|
H1 = Table header inserted by me.
H2 = Orginal header inserted by RS
D..= Detail records
To do this right click on the handle for the exisitng table header row and
click Insert Row Above. The formatting stayed when I downloaded the report
to Excel. Hope this helps.
"Jeff" wrote:
> Okay, I'll try my best to explain this....
> I have a table on my report. Above the header for 5 of my columns, I need
> to place a cell that spans all those columns. It looks like this:
> --
> | h |
> --
> | h | h | h | h | h |
> --
> | d | d | d | d | d |
> --
> h = header row
> d = detail row
> so, to do this I took the header cell for the left most column and merged it
> with the
> 4 other header cells. Then I put a rectangle into that cell, and drew a
> line through the middle to create the two level effect in the single header
> cell. Then, where each 'h' is in the above diagram, I put a text box with
> some text in it that serves as a label. So, basically all 5 of my detail
> columns have their own individual header, as well as a header that applies to
> all of them.
> When I run the report, and export it to PDF, everything looks great. When I
> export to excel, I get a strange effect. SRS seems to want to put the cell
> for the textbox in the bottom right most 'cell' in the header in a row below
> the other 4 in the second header 'row'.. So, it looks like this in Excel:
> --
> | h |
> --
> | h | h | h | h | |
> --
> | h |
> | --|
> | d | d | d | d | d |
> --
>
> h = header row
> d = detail row
> Anybody have any idea what's going on here? If I remove the 5th text box in
> the header (the one that's causing the problem), excel formats fine.
> It would be nice if I could merge cells across rows as well as columns,
> because that would make this problem trivial.
> Any help is greatly appreciated.
>
> Jeff
> Jeff|||Hmmm.
I vaguely remember trying something like this, but maybe I didn't set it up
right. I'll give it another shot. Thanks.
"bsod55" wrote:
> Jeff,
> Have you tried inserting a second table header row above the original table
> header row? Then do the merging on the inserted header row. I just did this
> on a report at my work. Doing so gave me this effect:
> | H1 |
> |H1|H2|H3|H4|
> |D1|D2|D3|D4|
> H1 = Table header inserted by me.
> H2 = Orginal header inserted by RS
> D..= Detail records
> To do this right click on the handle for the exisitng table header row and
> click Insert Row Above. The formatting stayed when I downloaded the report
> to Excel. Hope this helps.
> "Jeff" wrote:
> > Okay, I'll try my best to explain this....
> >
> > I have a table on my report. Above the header for 5 of my columns, I need
> > to place a cell that spans all those columns. It looks like this:
> >
> > --
> > | h |
> > --
> > | h | h | h | h | h |
> > --
> > | d | d | d | d | d |
> > --
> >
> > h = header row
> > d = detail row
> >
> > so, to do this I took the header cell for the left most column and merged it
> > with the
> > 4 other header cells. Then I put a rectangle into that cell, and drew a
> > line through the middle to create the two level effect in the single header
> > cell. Then, where each 'h' is in the above diagram, I put a text box with
> > some text in it that serves as a label. So, basically all 5 of my detail
> > columns have their own individual header, as well as a header that applies to
> > all of them.
> >
> > When I run the report, and export it to PDF, everything looks great. When I
> > export to excel, I get a strange effect. SRS seems to want to put the cell
> > for the textbox in the bottom right most 'cell' in the header in a row below
> > the other 4 in the second header 'row'.. So, it looks like this in Excel:
> >
> > --
> > | h |
> > --
> > | h | h | h | h | |
> > --
> > | h |
> > | --|
> > | d | d | d | d | d |
> > --
> >
> >
> > h = header row
> > d = detail row
> >
> > Anybody have any idea what's going on here? If I remove the 5th text box in
> > the header (the one that's causing the problem), excel formats fine.
> >
> > It would be nice if I could merge cells across rows as well as columns,
> > because that would make this problem trivial.
> >
> > Any help is greatly appreciated.
> >
> >
> > Jeff
> > Jeff
Showing posts with label report. Show all posts
Showing posts with label report. Show all posts
Thursday, March 29, 2012
Excel Formatting
I have a report that I exported to Excel which contains dates in one column.
About 10% of the dates show up as ######## accross the width of the cell.
The column is plenty wide enough and if you double-click one of these cells
the date shows up fine. It also does it on a column that has percentages.
Does anyone know how to prevent this from happening?What happens when you make the column very wide? Could it be trying to
format time in there as well?
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"BrianW" <BrianW@.discussions.microsoft.com> wrote in message
news:C87B46BC-65B1-4AB5-901E-E1707AFF4DA9@.microsoft.com...
>I have a report that I exported to Excel which contains dates in one
>column.
> About 10% of the dates show up as ######## accross the width of the cell.
> The column is plenty wide enough and if you double-click one of these
> cells
> the date shows up fine. It also does it on a column that has percentages.
> Does anyone know how to prevent this from happening?|||No. I made the column width 150 and it just added more # signs to fill up
the column. Is there a way I can send you the Excel file?
"Jeff A. Stucker" wrote:
> What happens when you make the column very wide? Could it be trying to
> format time in there as well?
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "BrianW" <BrianW@.discussions.microsoft.com> wrote in message
> news:C87B46BC-65B1-4AB5-901E-E1707AFF4DA9@.microsoft.com...
> >I have a report that I exported to Excel which contains dates in one
> >column.
> > About 10% of the dates show up as ######## accross the width of the cell.
> > The column is plenty wide enough and if you double-click one of these
> > cells
> > the date shows up fine. It also does it on a column that has percentages.
> > Does anyone know how to prevent this from happening?
>
>sql
About 10% of the dates show up as ######## accross the width of the cell.
The column is plenty wide enough and if you double-click one of these cells
the date shows up fine. It also does it on a column that has percentages.
Does anyone know how to prevent this from happening?What happens when you make the column very wide? Could it be trying to
format time in there as well?
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"BrianW" <BrianW@.discussions.microsoft.com> wrote in message
news:C87B46BC-65B1-4AB5-901E-E1707AFF4DA9@.microsoft.com...
>I have a report that I exported to Excel which contains dates in one
>column.
> About 10% of the dates show up as ######## accross the width of the cell.
> The column is plenty wide enough and if you double-click one of these
> cells
> the date shows up fine. It also does it on a column that has percentages.
> Does anyone know how to prevent this from happening?|||No. I made the column width 150 and it just added more # signs to fill up
the column. Is there a way I can send you the Excel file?
"Jeff A. Stucker" wrote:
> What happens when you make the column very wide? Could it be trying to
> format time in there as well?
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "BrianW" <BrianW@.discussions.microsoft.com> wrote in message
> news:C87B46BC-65B1-4AB5-901E-E1707AFF4DA9@.microsoft.com...
> >I have a report that I exported to Excel which contains dates in one
> >column.
> > About 10% of the dates show up as ######## accross the width of the cell.
> > The column is plenty wide enough and if you double-click one of these
> > cells
> > the date shows up fine. It also does it on a column that has percentages.
> > Does anyone know how to prevent this from happening?
>
>sql
Excel Format different from PDF and Image
I have a report that looks good in .PDF and .tif format, but really bad
in Excel format. Can anything be done about this?
Thank you!Carol,
At the heart of things is the fact that .PDF and .TIF simply render an
image of the report while Excel is trying to insert the entire report,
including headers and footers, into a viable spreadsheet.
Without seeing the Excel output, it's tough to know for sure what
issues you're having but typically the problem with Excel is it inserts
additional columns (and sometimes rows as well) that don't exist in the
original report design.
The cause is that the left and right borders of some report objects
(text boxes, etc.) are not lining up in the different report sections
and/or data regions. For example, if there's a text box in the page
header that's 1" wide and then a 1.25" wide table column in the body
(under the 1" header text box), Excel will render that into two
columns. That's a pretty basic example but the problem greatly
exacerbates if you're using free-form data regions or multiple tables
or tables with subreports.
Unfortunately, the only way to resolve this is to manipulate everything
in the report design to line up as much as possible. It helps to use
the various width and height properties to set things to match up
exactly as opposed to relying just on "eyeballing" it.
Hope this helps.
in Excel format. Can anything be done about this?
Thank you!Carol,
At the heart of things is the fact that .PDF and .TIF simply render an
image of the report while Excel is trying to insert the entire report,
including headers and footers, into a viable spreadsheet.
Without seeing the Excel output, it's tough to know for sure what
issues you're having but typically the problem with Excel is it inserts
additional columns (and sometimes rows as well) that don't exist in the
original report design.
The cause is that the left and right borders of some report objects
(text boxes, etc.) are not lining up in the different report sections
and/or data regions. For example, if there's a text box in the page
header that's 1" wide and then a 1.25" wide table column in the body
(under the 1" header text box), Excel will render that into two
columns. That's a pretty basic example but the problem greatly
exacerbates if you're using free-form data regions or multiple tables
or tables with subreports.
Unfortunately, the only way to resolve this is to manipulate everything
in the report design to line up as much as possible. It helps to use
the various width and height properties to set things to match up
exactly as opposed to relying just on "eyeballing" it.
Hope this helps.
Excel files are too large
I have the following problem with Reporting Services:
My report has about 6500 lines and 100 columns. When I export it into Excel
the size of the end file is about 20 Mb. As I have to send it using
subscriptions, it is a problem â' too large file for e-mail. Are there any
ways to minimize the size of output Excel file?
Regards,
Boris.Workaround:
Create a webpage containing your report, post it on the webserver, and
e-mail a link to this page to your customer.
It is faster, and more friendly designed ( and it began to be a
standard in modern distributed applications)
You also have to take care about "Garbage Collection": set an
expiration date for reports to be deleted from the webserver.
Have fun :)|||Are you using Service Pack 1? We did some sizing work but it still might be
too big for you.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Boris" <frolovBA@.trytoguessHM.com> wrote in message
news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
>I have the following problem with Reporting Services:
> My report has about 6500 lines and 100 columns. When I export it into
> Excel
> the size of the end file is about 20 Mb. As I have to send it using
> subscriptions, it is a problem - too large file for e-mail. Are there any
> ways to minimize the size of output Excel file?
> Regards,
> Boris.
>|||Thank you for your advice, but users of this report want to receive it in
Excel.
Iâ've made a workaround: Reporting Services save the Excel file into
directory and then my program archive it and send it through e-mail. But may
be I miss some details that can optimize the size of Report?
Regards,
Boris
"katzirina" wrote:
> Workaround:
> Create a webpage containing your report, post it on the webserver, and
> e-mail a link to this page to your customer.
> It is faster, and more friendly designed ( and it began to be a
> standard in modern distributed applications)
> You also have to take care about "Garbage Collection": set an
> expiration date for reports to be deleted from the webserver.
> Have fun :)
>|||Yes I use SP1.
Regards,
Boris.
"Brian Welcker [MS]" wrote:
> Are you using Service Pack 1? We did some sizing work but it still might be
> too big for you.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
> news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
> >I have the following problem with Reporting Services:
> > My report has about 6500 lines and 100 columns. When I export it into
> > Excel
> > the size of the end file is about 20 Mb. As I have to send it using
> > subscriptions, it is a problem - too large file for e-mail. Are there any
> > ways to minimize the size of output Excel file?
> >
> > Regards,
> > Boris.
> >
>
>|||When you create the spreadsheet manually, how large is it? I just tried a
very simple sheet with no formatting and a single number per cell and it was
5 MB. The only way this would work through compression in the delivery
provider. We do not support this but there might be a 3rd party that does.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Boris" <frolovBA@.trytoguessHM.com> wrote in message
news:6A26B3A5-0CF5-4F3B-8B1A-3CB4F36B453E@.microsoft.com...
> Yes I use SP1.
> Regards,
> Boris.
> "Brian Welcker [MS]" wrote:
>> Are you using Service Pack 1? We did some sizing work but it still might
>> be
>> too big for you.
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
>> news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
>> >I have the following problem with Reporting Services:
>> > My report has about 6500 lines and 100 columns. When I export it into
>> > Excel
>> > the size of the end file is about 20 Mb. As I have to send it using
>> > subscriptions, it is a problem - too large file for e-mail. Are there
>> > any
>> > ways to minimize the size of output Excel file?
>> >
>> > Regards,
>> > Boris.
>> >
>>|||When I create it manually itâ's about 6 Mb. Even if I made export to Excel
from Reporting Server, then open this 24 Mb file and save it â' it gets size
about 7 Mb. The only formatting I use are 0.5pt borders and number/date
formats.
Regards,
Boris.
"Brian Welcker [MS]" wrote:
> When you create the spreadsheet manually, how large is it? I just tried a
> very simple sheet with no formatting and a single number per cell and it was
> 5 MB. The only way this would work through compression in the delivery
> provider. We do not support this but there might be a 3rd party that does.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
> news:6A26B3A5-0CF5-4F3B-8B1A-3CB4F36B453E@.microsoft.com...
> > Yes I use SP1.
> >
> > Regards,
> > Boris.
> >
> > "Brian Welcker [MS]" wrote:
> >
> >> Are you using Service Pack 1? We did some sizing work but it still might
> >> be
> >> too big for you.
> >>
> >> --
> >> Brian Welcker
> >> Group Program Manager
> >> Microsoft SQL Server
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
> >> news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
> >> >I have the following problem with Reporting Services:
> >> > My report has about 6500 lines and 100 columns. When I export it into
> >> > Excel
> >> > the size of the end file is about 20 Mb. As I have to send it using
> >> > subscriptions, it is a problem - too large file for e-mail. Are there
> >> > any
> >> > ways to minimize the size of output Excel file?
> >> >
> >> > Regards,
> >> > Boris.
> >> >
> >>
> >>
> >>
>
>
My report has about 6500 lines and 100 columns. When I export it into Excel
the size of the end file is about 20 Mb. As I have to send it using
subscriptions, it is a problem â' too large file for e-mail. Are there any
ways to minimize the size of output Excel file?
Regards,
Boris.Workaround:
Create a webpage containing your report, post it on the webserver, and
e-mail a link to this page to your customer.
It is faster, and more friendly designed ( and it began to be a
standard in modern distributed applications)
You also have to take care about "Garbage Collection": set an
expiration date for reports to be deleted from the webserver.
Have fun :)|||Are you using Service Pack 1? We did some sizing work but it still might be
too big for you.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Boris" <frolovBA@.trytoguessHM.com> wrote in message
news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
>I have the following problem with Reporting Services:
> My report has about 6500 lines and 100 columns. When I export it into
> Excel
> the size of the end file is about 20 Mb. As I have to send it using
> subscriptions, it is a problem - too large file for e-mail. Are there any
> ways to minimize the size of output Excel file?
> Regards,
> Boris.
>|||Thank you for your advice, but users of this report want to receive it in
Excel.
Iâ've made a workaround: Reporting Services save the Excel file into
directory and then my program archive it and send it through e-mail. But may
be I miss some details that can optimize the size of Report?
Regards,
Boris
"katzirina" wrote:
> Workaround:
> Create a webpage containing your report, post it on the webserver, and
> e-mail a link to this page to your customer.
> It is faster, and more friendly designed ( and it began to be a
> standard in modern distributed applications)
> You also have to take care about "Garbage Collection": set an
> expiration date for reports to be deleted from the webserver.
> Have fun :)
>|||Yes I use SP1.
Regards,
Boris.
"Brian Welcker [MS]" wrote:
> Are you using Service Pack 1? We did some sizing work but it still might be
> too big for you.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
> news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
> >I have the following problem with Reporting Services:
> > My report has about 6500 lines and 100 columns. When I export it into
> > Excel
> > the size of the end file is about 20 Mb. As I have to send it using
> > subscriptions, it is a problem - too large file for e-mail. Are there any
> > ways to minimize the size of output Excel file?
> >
> > Regards,
> > Boris.
> >
>
>|||When you create the spreadsheet manually, how large is it? I just tried a
very simple sheet with no formatting and a single number per cell and it was
5 MB. The only way this would work through compression in the delivery
provider. We do not support this but there might be a 3rd party that does.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Boris" <frolovBA@.trytoguessHM.com> wrote in message
news:6A26B3A5-0CF5-4F3B-8B1A-3CB4F36B453E@.microsoft.com...
> Yes I use SP1.
> Regards,
> Boris.
> "Brian Welcker [MS]" wrote:
>> Are you using Service Pack 1? We did some sizing work but it still might
>> be
>> too big for you.
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
>> news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
>> >I have the following problem with Reporting Services:
>> > My report has about 6500 lines and 100 columns. When I export it into
>> > Excel
>> > the size of the end file is about 20 Mb. As I have to send it using
>> > subscriptions, it is a problem - too large file for e-mail. Are there
>> > any
>> > ways to minimize the size of output Excel file?
>> >
>> > Regards,
>> > Boris.
>> >
>>|||When I create it manually itâ's about 6 Mb. Even if I made export to Excel
from Reporting Server, then open this 24 Mb file and save it â' it gets size
about 7 Mb. The only formatting I use are 0.5pt borders and number/date
formats.
Regards,
Boris.
"Brian Welcker [MS]" wrote:
> When you create the spreadsheet manually, how large is it? I just tried a
> very simple sheet with no formatting and a single number per cell and it was
> 5 MB. The only way this would work through compression in the delivery
> provider. We do not support this but there might be a 3rd party that does.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
> news:6A26B3A5-0CF5-4F3B-8B1A-3CB4F36B453E@.microsoft.com...
> > Yes I use SP1.
> >
> > Regards,
> > Boris.
> >
> > "Brian Welcker [MS]" wrote:
> >
> >> Are you using Service Pack 1? We did some sizing work but it still might
> >> be
> >> too big for you.
> >>
> >> --
> >> Brian Welcker
> >> Group Program Manager
> >> Microsoft SQL Server
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
> >> news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
> >> >I have the following problem with Reporting Services:
> >> > My report has about 6500 lines and 100 columns. When I export it into
> >> > Excel
> >> > the size of the end file is about 20 Mb. As I have to send it using
> >> > subscriptions, it is a problem - too large file for e-mail. Are there
> >> > any
> >> > ways to minimize the size of output Excel file?
> >> >
> >> > Regards,
> >> > Boris.
> >> >
> >>
> >>
> >>
>
>
Tuesday, March 27, 2012
Excel file size - huge! - on Prod server
When I run a report in Reporting Services on the Report Server on my
local PC, I can save the report to Excel as reasonable file sizes eg.
700K. When I deploy the same report's rdl to the live server, run it
and then save the same report to my network share, the file size
explodes to several meg (anything from 5mb to 15 mb). Anyone know why
this happens and how I can prevent it?My guess is that your local one has SP1 and the live one does not. SP1
changed to native format instead of mhtml.
Check versions by going to //yourserver/reportserver
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Vivienne" <vivienne00@.yahoo.com> wrote in message
news:1107967800.202356.71560@.c13g2000cwb.googlegroups.com...
> When I run a report in Reporting Services on the Report Server on my
> local PC, I can save the report to Excel as reasonable file sizes eg.
> 700K. When I deploy the same report's rdl to the live server, run it
> and then save the same report to my network share, the file size
> explodes to several meg (anything from 5mb to 15 mb). Anyone know why
> this happens and how I can prevent it?
>
local PC, I can save the report to Excel as reasonable file sizes eg.
700K. When I deploy the same report's rdl to the live server, run it
and then save the same report to my network share, the file size
explodes to several meg (anything from 5mb to 15 mb). Anyone know why
this happens and how I can prevent it?My guess is that your local one has SP1 and the live one does not. SP1
changed to native format instead of mhtml.
Check versions by going to //yourserver/reportserver
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Vivienne" <vivienne00@.yahoo.com> wrote in message
news:1107967800.202356.71560@.c13g2000cwb.googlegroups.com...
> When I run a report in Reporting Services on the Report Server on my
> local PC, I can save the report to Excel as reasonable file sizes eg.
> 700K. When I deploy the same report's rdl to the live server, run it
> and then save the same report to my network share, the file size
> explodes to several meg (anything from 5mb to 15 mb). Anyone know why
> this happens and how I can prevent it?
>
Excel Exports Hidden Images
Hello,
I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
has a remedy. My report contains a table with an image on the detail row
whose visibility is toggled based on a value. Everything works as expected
when viewing the report onscreen or exporting to PDF. However, the Excel
Export ignores the visibility expression and displays the image for every
detail row. Any thoughts or workarounds?
Thanks in advance!
KathyOn Jul 6, 10:44 am, Kathy <K...@.discussions.microsoft.com> wrote:
> Hello,
> I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
> has a remedy. My report contains a table with an image on the detail row
> whose visibility is toggled based on a value. Everything works as expected
> when viewing the report onscreen or exporting to PDF. However, the Excel
> Export ignores the visibility expression and displays the image for every
> detail row. Any thoughts or workarounds?
> Thanks in advance!
> Kathy
As far as I know, you are correct. Hopefully this will be corrected in
a future SP or in SSRS 2008. Sorry that I could not be of further
assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||Thank you for the quick response. Have a lovely day!
"EMartinez" wrote:
> On Jul 6, 10:44 am, Kathy <K...@.discussions.microsoft.com> wrote:
> > Hello,
> >
> > I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
> > has a remedy. My report contains a table with an image on the detail row
> > whose visibility is toggled based on a value. Everything works as expected
> > when viewing the report onscreen or exporting to PDF. However, the Excel
> > Export ignores the visibility expression and displays the image for every
> > detail row. Any thoughts or workarounds?
> >
> > Thanks in advance!
> > Kathy
>
> As far as I know, you are correct. Hopefully this will be corrected in
> a future SP or in SSRS 2008. Sorry that I could not be of further
> assistance.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Jul 9, 8:38 am, Kathy <K...@.discussions.microsoft.com> wrote:
> Thank you for the quick response. Have a lovely day!
> "EMartinez" wrote:
> > On Jul 6, 10:44 am, Kathy <K...@.discussions.microsoft.com> wrote:
> > > Hello,
> > > I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
> > > has a remedy. My report contains a table with an image on the detail row
> > > whose visibility is toggled based on a value. Everything works as expected
> > > when viewing the report onscreen or exporting to PDF. However, the Excel
> > > Export ignores the visibility expression and displays the image for every
> > > detail row. Any thoughts or workarounds?
> > > Thanks in advance!
> > > Kathy
> > As far as I know, you are correct. Hopefully this will be corrected in
> > a future SP or in SSRS 2008. Sorry that I could not be of further
> > assistance.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
You're welcome. Let me know if I can be of further assistance.
Regards,
Enrique Martinez
Sr. Software Consultant
I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
has a remedy. My report contains a table with an image on the detail row
whose visibility is toggled based on a value. Everything works as expected
when viewing the report onscreen or exporting to PDF. However, the Excel
Export ignores the visibility expression and displays the image for every
detail row. Any thoughts or workarounds?
Thanks in advance!
KathyOn Jul 6, 10:44 am, Kathy <K...@.discussions.microsoft.com> wrote:
> Hello,
> I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
> has a remedy. My report contains a table with an image on the detail row
> whose visibility is toggled based on a value. Everything works as expected
> when viewing the report onscreen or exporting to PDF. However, the Excel
> Export ignores the visibility expression and displays the image for every
> detail row. Any thoughts or workarounds?
> Thanks in advance!
> Kathy
As far as I know, you are correct. Hopefully this will be corrected in
a future SP or in SSRS 2008. Sorry that I could not be of further
assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||Thank you for the quick response. Have a lovely day!
"EMartinez" wrote:
> On Jul 6, 10:44 am, Kathy <K...@.discussions.microsoft.com> wrote:
> > Hello,
> >
> > I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
> > has a remedy. My report contains a table with an image on the detail row
> > whose visibility is toggled based on a value. Everything works as expected
> > when viewing the report onscreen or exporting to PDF. However, the Excel
> > Export ignores the visibility expression and displays the image for every
> > detail row. Any thoughts or workarounds?
> >
> > Thanks in advance!
> > Kathy
>
> As far as I know, you are correct. Hopefully this will be corrected in
> a future SP or in SSRS 2008. Sorry that I could not be of further
> assistance.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Jul 9, 8:38 am, Kathy <K...@.discussions.microsoft.com> wrote:
> Thank you for the quick response. Have a lovely day!
> "EMartinez" wrote:
> > On Jul 6, 10:44 am, Kathy <K...@.discussions.microsoft.com> wrote:
> > > Hello,
> > > I think this may be a bug with SSRS 2005 but wanted to verify in case anyone
> > > has a remedy. My report contains a table with an image on the detail row
> > > whose visibility is toggled based on a value. Everything works as expected
> > > when viewing the report onscreen or exporting to PDF. However, the Excel
> > > Export ignores the visibility expression and displays the image for every
> > > detail row. Any thoughts or workarounds?
> > > Thanks in advance!
> > > Kathy
> > As far as I know, you are correct. Hopefully this will be corrected in
> > a future SP or in SSRS 2008. Sorry that I could not be of further
> > assistance.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
You're welcome. Let me know if I can be of further assistance.
Regards,
Enrique Martinez
Sr. Software Consultant
Excel Exporting results in MIME message
I reviewed all post but have not seen the problem I have.
When exporting a report to Excel (regardless if I save or open the file) my
output is a multi-part MIME message. I get only one worksheet (there are 4
pages in the report) and it has the name of the exported report.
There is a section for each page in this message and a StyleSheet section.
Did I miss something in the report Services set-up?
Thanks
ShawnI took a better look at the rest of the posts and did find some with the same
problem. One of them suggested installation of SP1 in MS Office 2000. My
problem now is that I did install SP1 and nothing changed. If anyone has
another suggestion it will be greatly appreciated.
Thanks
Shawn
"Shawn Kralj" wrote:
> I reviewed all post but have not seen the problem I have.
> When exporting a report to Excel (regardless if I save or open the file) my
> output is a multi-part MIME message. I get only one worksheet (there are 4
> pages in the report) and it has the name of the exported report.
> There is a section for each page in this message and a StyleSheet section.
> Did I miss something in the report Services set-up?
> Thanks
> Shawn|||Close, it is not SP1. It is SP1 for Reporting Services that has the fix. SP1
no longer uses the MIME format.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Shawn Kralj" <ShawnKralj@.discussions.microsoft.com> wrote in message
news:FE6555D6-71F4-4C29-90F4-DA92604B4816@.microsoft.com...
> I took a better look at the rest of the posts and did find some with the
same
> problem. One of them suggested installation of SP1 in MS Office 2000. My
> problem now is that I did install SP1 and nothing changed. If anyone has
> another suggestion it will be greatly appreciated.
> Thanks
> Shawn
> "Shawn Kralj" wrote:
> > I reviewed all post but have not seen the problem I have.
> >
> > When exporting a report to Excel (regardless if I save or open the file)
my
> > output is a multi-part MIME message. I get only one worksheet (there are
4
> > pages in the report) and it has the name of the exported report.
> >
> > There is a section for each page in this message and a StyleSheet
section.
> >
> > Did I miss something in the report Services set-up?
> >
> > Thanks
> >
> > Shawn|||Thanks Bruce. That worked. Installing SP1 for Reporting Services fixed the
problem.
Looks great.
Shawn
"Bruce L-C [MVP]" wrote:
> Close, it is not SP1. It is SP1 for Reporting Services that has the fix. SP1
> no longer uses the MIME format.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Shawn Kralj" <ShawnKralj@.discussions.microsoft.com> wrote in message
> news:FE6555D6-71F4-4C29-90F4-DA92604B4816@.microsoft.com...
> > I took a better look at the rest of the posts and did find some with the
> same
> > problem. One of them suggested installation of SP1 in MS Office 2000. My
> > problem now is that I did install SP1 and nothing changed. If anyone has
> > another suggestion it will be greatly appreciated.
> >
> > Thanks
> >
> > Shawn
> >
> > "Shawn Kralj" wrote:
> >
> > > I reviewed all post but have not seen the problem I have.
> > >
> > > When exporting a report to Excel (regardless if I save or open the file)
> my
> > > output is a multi-part MIME message. I get only one worksheet (there are
> 4
> > > pages in the report) and it has the name of the exported report.
> > >
> > > There is a section for each page in this message and a StyleSheet
> section.
> > >
> > > Did I miss something in the report Services set-up?
> > >
> > > Thanks
> > >
> > > Shawn
>
>
When exporting a report to Excel (regardless if I save or open the file) my
output is a multi-part MIME message. I get only one worksheet (there are 4
pages in the report) and it has the name of the exported report.
There is a section for each page in this message and a StyleSheet section.
Did I miss something in the report Services set-up?
Thanks
ShawnI took a better look at the rest of the posts and did find some with the same
problem. One of them suggested installation of SP1 in MS Office 2000. My
problem now is that I did install SP1 and nothing changed. If anyone has
another suggestion it will be greatly appreciated.
Thanks
Shawn
"Shawn Kralj" wrote:
> I reviewed all post but have not seen the problem I have.
> When exporting a report to Excel (regardless if I save or open the file) my
> output is a multi-part MIME message. I get only one worksheet (there are 4
> pages in the report) and it has the name of the exported report.
> There is a section for each page in this message and a StyleSheet section.
> Did I miss something in the report Services set-up?
> Thanks
> Shawn|||Close, it is not SP1. It is SP1 for Reporting Services that has the fix. SP1
no longer uses the MIME format.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Shawn Kralj" <ShawnKralj@.discussions.microsoft.com> wrote in message
news:FE6555D6-71F4-4C29-90F4-DA92604B4816@.microsoft.com...
> I took a better look at the rest of the posts and did find some with the
same
> problem. One of them suggested installation of SP1 in MS Office 2000. My
> problem now is that I did install SP1 and nothing changed. If anyone has
> another suggestion it will be greatly appreciated.
> Thanks
> Shawn
> "Shawn Kralj" wrote:
> > I reviewed all post but have not seen the problem I have.
> >
> > When exporting a report to Excel (regardless if I save or open the file)
my
> > output is a multi-part MIME message. I get only one worksheet (there are
4
> > pages in the report) and it has the name of the exported report.
> >
> > There is a section for each page in this message and a StyleSheet
section.
> >
> > Did I miss something in the report Services set-up?
> >
> > Thanks
> >
> > Shawn|||Thanks Bruce. That worked. Installing SP1 for Reporting Services fixed the
problem.
Looks great.
Shawn
"Bruce L-C [MVP]" wrote:
> Close, it is not SP1. It is SP1 for Reporting Services that has the fix. SP1
> no longer uses the MIME format.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Shawn Kralj" <ShawnKralj@.discussions.microsoft.com> wrote in message
> news:FE6555D6-71F4-4C29-90F4-DA92604B4816@.microsoft.com...
> > I took a better look at the rest of the posts and did find some with the
> same
> > problem. One of them suggested installation of SP1 in MS Office 2000. My
> > problem now is that I did install SP1 and nothing changed. If anyone has
> > another suggestion it will be greatly appreciated.
> >
> > Thanks
> >
> > Shawn
> >
> > "Shawn Kralj" wrote:
> >
> > > I reviewed all post but have not seen the problem I have.
> > >
> > > When exporting a report to Excel (regardless if I save or open the file)
> my
> > > output is a multi-part MIME message. I get only one worksheet (there are
> 4
> > > pages in the report) and it has the name of the exported report.
> > >
> > > There is a section for each page in this message and a StyleSheet
> section.
> > >
> > > Did I miss something in the report Services set-up?
> > >
> > > Thanks
> > >
> > > Shawn
>
>
Excel Export-Extra columns
Hi,
I am trying to export my report to Excel.When I do this I get some extra columns(blank though) in the Excel sheet which r not there in my report.And I see some greentips in some of my cells in excel sheet(which is a warning that a number is exported as text).Why r this due to?How can i remove these?
Thank You,When you are using a list in your report, this will most likely happen as we
have to approximate the cell layout. Table and matrix work much better when
exporting. Also, make sure you have number formats on your values so they
will get explicit formats in Excel.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sudha" <Sudha@.discussions.microsoft.com> wrote in message
news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
> Hi,
> I am trying to export my report to Excel.When I do this I get some extra
> columns(blank though) in the Excel sheet which r not there in my
> report.And I see some greentips in some of my cells in excel sheet(which
> is a warning that a number is exported as text).Why r this due to?How can
> i remove these?
> Thank You,|||Hi,
I am using only tables/matrix in my reports and not lists still i get some extra columns.How can i avoid this?
Thanx
"Brian Welcker [MSFT]" wrote:
> When you are using a list in your report, this will most likely happen as we
> have to approximate the cell layout. Table and matrix work much better when
> exporting. Also, make sure you have number formats on your values so they
> will get explicit formats in Excel.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
> news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
> > Hi,
> >
> > I am trying to export my report to Excel.When I do this I get some extra
> > columns(blank though) in the Excel sheet which r not there in my
> > report.And I see some greentips in some of my cells in excel sheet(which
> > is a warning that a number is exported as text).Why r this due to?How can
> > i remove these?
> >
> > Thank You,
>
>|||Do you have page headers and footers? This can cause this as well. And when
you say you have tables / matrices, you mean in different reports, right? If
this is not the case, it would be interesting to see your reports and the
Excel output.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sudha" <Sudha@.discussions.microsoft.com> wrote in message
news:53373429-2B5D-4335-8113-819A969B3C15@.microsoft.com...
> Hi,
> I am using only tables/matrix in my reports and not lists still i get some
> extra columns.How can i avoid this?
> Thanx
> "Brian Welcker [MSFT]" wrote:
>> When you are using a list in your report, this will most likely happen as
>> we
>> have to approximate the cell layout. Table and matrix work much better
>> when
>> exporting. Also, make sure you have number formats on your values so they
>> will get explicit formats in Excel.
>> --
>> Brian Welcker
>> Group Program Manager
>> SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
>> news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
>> > Hi,
>> >
>> > I am trying to export my report to Excel.When I do this I get some
>> > extra
>> > columns(blank though) in the Excel sheet which r not there in my
>> > report.And I see some greentips in some of my cells in excel
>> > sheet(which
>> > is a warning that a number is exported as text).Why r this due to?How
>> > can
>> > i remove these?
>> >
>> > Thank You,
>>|||I am using a table for my report and I'm not implementing a header nor
a footer. In the end of the table though, I used a line and a textbox
to somehow "appear as a footer" at the end of the report.
Upon export to excel, extra columns were inserted and I don't know how
does this happened or how I can remove them.
I'll be more than willing to provide you with screenshots of the
report in the designer view and its output in excel.
I hope you can advice me on this matter and any help will be greatly
appreciated.
Have a nice day and thanks in advance.
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message news:<uh5BAZMYEHA.3260@.tk2msftngp13.phx.gbl>...
> Do you have page headers and footers? This can cause this as well. And when
> you say you have tables / matrices, you mean in different reports, right? If
> this is not the case, it would be interesting to see your reports and the
> Excel output.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
> news:53373429-2B5D-4335-8113-819A969B3C15@.microsoft.com...
> > Hi,
> >
> > I am using only tables/matrix in my reports and not lists still i get some
> > extra columns.How can i avoid this?
> >
> > Thanx
> >
> > "Brian Welcker [MSFT]" wrote:
> >
> >> When you are using a list in your report, this will most likely happen as
> >> we
> >> have to approximate the cell layout. Table and matrix work much better
> >> when
> >> exporting. Also, make sure you have number formats on your values so they
> >> will get explicit formats in Excel.
> >>
> >> --
> >> Brian Welcker
> >> Group Program Manager
> >> SQL Server Reporting Services
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
> >> news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
> >> > Hi,
> >> >
> >> > I am trying to export my report to Excel.When I do this I get some
> >> > extra
> >> > columns(blank though) in the Excel sheet which r not there in my
> >> > report.And I see some greentips in some of my cells in excel
> >> > sheet(which
> >> > is a warning that a number is exported as text).Why r this due to?How
> >> > can
> >> > i remove these?
> >> >
> >> > Thank You,
> >>
> >>
> >>
I am trying to export my report to Excel.When I do this I get some extra columns(blank though) in the Excel sheet which r not there in my report.And I see some greentips in some of my cells in excel sheet(which is a warning that a number is exported as text).Why r this due to?How can i remove these?
Thank You,When you are using a list in your report, this will most likely happen as we
have to approximate the cell layout. Table and matrix work much better when
exporting. Also, make sure you have number formats on your values so they
will get explicit formats in Excel.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sudha" <Sudha@.discussions.microsoft.com> wrote in message
news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
> Hi,
> I am trying to export my report to Excel.When I do this I get some extra
> columns(blank though) in the Excel sheet which r not there in my
> report.And I see some greentips in some of my cells in excel sheet(which
> is a warning that a number is exported as text).Why r this due to?How can
> i remove these?
> Thank You,|||Hi,
I am using only tables/matrix in my reports and not lists still i get some extra columns.How can i avoid this?
Thanx
"Brian Welcker [MSFT]" wrote:
> When you are using a list in your report, this will most likely happen as we
> have to approximate the cell layout. Table and matrix work much better when
> exporting. Also, make sure you have number formats on your values so they
> will get explicit formats in Excel.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
> news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
> > Hi,
> >
> > I am trying to export my report to Excel.When I do this I get some extra
> > columns(blank though) in the Excel sheet which r not there in my
> > report.And I see some greentips in some of my cells in excel sheet(which
> > is a warning that a number is exported as text).Why r this due to?How can
> > i remove these?
> >
> > Thank You,
>
>|||Do you have page headers and footers? This can cause this as well. And when
you say you have tables / matrices, you mean in different reports, right? If
this is not the case, it would be interesting to see your reports and the
Excel output.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sudha" <Sudha@.discussions.microsoft.com> wrote in message
news:53373429-2B5D-4335-8113-819A969B3C15@.microsoft.com...
> Hi,
> I am using only tables/matrix in my reports and not lists still i get some
> extra columns.How can i avoid this?
> Thanx
> "Brian Welcker [MSFT]" wrote:
>> When you are using a list in your report, this will most likely happen as
>> we
>> have to approximate the cell layout. Table and matrix work much better
>> when
>> exporting. Also, make sure you have number formats on your values so they
>> will get explicit formats in Excel.
>> --
>> Brian Welcker
>> Group Program Manager
>> SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
>> news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
>> > Hi,
>> >
>> > I am trying to export my report to Excel.When I do this I get some
>> > extra
>> > columns(blank though) in the Excel sheet which r not there in my
>> > report.And I see some greentips in some of my cells in excel
>> > sheet(which
>> > is a warning that a number is exported as text).Why r this due to?How
>> > can
>> > i remove these?
>> >
>> > Thank You,
>>|||I am using a table for my report and I'm not implementing a header nor
a footer. In the end of the table though, I used a line and a textbox
to somehow "appear as a footer" at the end of the report.
Upon export to excel, extra columns were inserted and I don't know how
does this happened or how I can remove them.
I'll be more than willing to provide you with screenshots of the
report in the designer view and its output in excel.
I hope you can advice me on this matter and any help will be greatly
appreciated.
Have a nice day and thanks in advance.
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message news:<uh5BAZMYEHA.3260@.tk2msftngp13.phx.gbl>...
> Do you have page headers and footers? This can cause this as well. And when
> you say you have tables / matrices, you mean in different reports, right? If
> this is not the case, it would be interesting to see your reports and the
> Excel output.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
> news:53373429-2B5D-4335-8113-819A969B3C15@.microsoft.com...
> > Hi,
> >
> > I am using only tables/matrix in my reports and not lists still i get some
> > extra columns.How can i avoid this?
> >
> > Thanx
> >
> > "Brian Welcker [MSFT]" wrote:
> >
> >> When you are using a list in your report, this will most likely happen as
> >> we
> >> have to approximate the cell layout. Table and matrix work much better
> >> when
> >> exporting. Also, make sure you have number formats on your values so they
> >> will get explicit formats in Excel.
> >>
> >> --
> >> Brian Welcker
> >> Group Program Manager
> >> SQL Server Reporting Services
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
> >> news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
> >> > Hi,
> >> >
> >> > I am trying to export my report to Excel.When I do this I get some
> >> > extra
> >> > columns(blank though) in the Excel sheet which r not there in my
> >> > report.And I see some greentips in some of my cells in excel
> >> > sheet(which
> >> > is a warning that a number is exported as text).Why r this due to?How
> >> > can
> >> > i remove these?
> >> >
> >> > Thank You,
> >>
> >>
> >>
excel export...
Hi Guys
When exporting my report to excel my field text gets exported as double
lines. Does anybody know a way around this?
eg:
Line 1
Line 2
turns to
Line 1
Line 2
Thanks
KezHi,
If the space between two rows are more than 0.125 in, then this is the limit
it removes automatically when export to excel. Try reducing your row height
and see how excel renders.
Amarnath.
"Kez" wrote:
> Hi Guys
> When exporting my report to excel my field text gets exported as double
> lines. Does anybody know a way around this?
> eg:
> Line 1
> Line 2
> turns to
> Line 1
> Line 2
>
> Thanks
> Kez|||Thanks
That did the trick
"Amarnath" wrote:
> Hi,
> If the space between two rows are more than 0.125 in, then this is the limit
> it removes automatically when export to excel. Try reducing your row height
> and see how excel renders.
> Amarnath.
>
> "Kez" wrote:
> > Hi Guys
> > When exporting my report to excel my field text gets exported as double
> > lines. Does anybody know a way around this?
> >
> > eg:
> > Line 1
> > Line 2
> >
> > turns to
> > Line 1
> >
> > Line 2
> >
> >
> > Thanks
> > Kez
When exporting my report to excel my field text gets exported as double
lines. Does anybody know a way around this?
eg:
Line 1
Line 2
turns to
Line 1
Line 2
Thanks
KezHi,
If the space between two rows are more than 0.125 in, then this is the limit
it removes automatically when export to excel. Try reducing your row height
and see how excel renders.
Amarnath.
"Kez" wrote:
> Hi Guys
> When exporting my report to excel my field text gets exported as double
> lines. Does anybody know a way around this?
> eg:
> Line 1
> Line 2
> turns to
> Line 1
> Line 2
>
> Thanks
> Kez|||Thanks
That did the trick
"Amarnath" wrote:
> Hi,
> If the space between two rows are more than 0.125 in, then this is the limit
> it removes automatically when export to excel. Try reducing your row height
> and see how excel renders.
> Amarnath.
>
> "Kez" wrote:
> > Hi Guys
> > When exporting my report to excel my field text gets exported as double
> > lines. Does anybody know a way around this?
> >
> > eg:
> > Line 1
> > Line 2
> >
> > turns to
> > Line 1
> >
> > Line 2
> >
> >
> > Thanks
> > Kez
Excel Export Troubles
I have a local report that I am trying to export to Excel. It uses a stored procedure( SQL 2005) as the data source. The stored procedure runs in 2 seconds and returns about 8000 rows. The export to excel never completes(does work if I limit the number of rows returned). I have set the executionTimeout="36000" in the web.config and set the table adapters Command timeout in the code high enough so that I am not getting timeout errors. The export to PDF works, though takes a few minutes. Looking for any thoughts or ideas on why Excel is so slow.
Here is one idea. Use a SqlDataAdapter and fill a DataSet using your Store Proc then use this free dll to export the DataSet data into CSV file. Excel can easily read the csv and you can format the report in any way you need to.
Here is the link: http://apriendavisualstudio.net/?p=23
Try it, it very simple nothing fancy. It works for me.
sql
Excel Export Report Footer Problem
We have a footer in our reports which displays a disclaimer in a textbox.
The disclaimer shows up fine when exported to PDF, but when exported to Excel
it chops off everything but the first 255 chars. Can someone explain why
this is happening?Frank,
How do you hide Footer for Browser/Web View and enable it only for Email
Subscription ( Email / Pdf / MHTML ) format. Is it possible to add Disclaimer
text on the Create Subscription Web method.
Let me know pls.
Thanks!
"Frank Hoover" wrote:
> We have a footer in our reports which displays a disclaimer in a textbox.
> The disclaimer shows up fine when exported to PDF, but when exported to Excel
> it chops off everything but the first 255 chars. Can someone explain why
> this is happening?|||I read in the documentation that excel has a limit of 255 characters for the
footer - looks like you hit the limit.
"Frank Hoover" wrote:
> We have a footer in our reports which displays a disclaimer in a textbox.
> The disclaimer shows up fine when exported to PDF, but when exported to Excel
> it chops off everything but the first 255 chars. Can someone explain why
> this is happening?
The disclaimer shows up fine when exported to PDF, but when exported to Excel
it chops off everything but the first 255 chars. Can someone explain why
this is happening?Frank,
How do you hide Footer for Browser/Web View and enable it only for Email
Subscription ( Email / Pdf / MHTML ) format. Is it possible to add Disclaimer
text on the Create Subscription Web method.
Let me know pls.
Thanks!
"Frank Hoover" wrote:
> We have a footer in our reports which displays a disclaimer in a textbox.
> The disclaimer shows up fine when exported to PDF, but when exported to Excel
> it chops off everything but the first 255 chars. Can someone explain why
> this is happening?|||I read in the documentation that excel has a limit of 255 characters for the
footer - looks like you hit the limit.
"Frank Hoover" wrote:
> We have a footer in our reports which displays a disclaimer in a textbox.
> The disclaimer shows up fine when exported to PDF, but when exported to Excel
> it chops off everything but the first 255 chars. Can someone explain why
> this is happening?
Excel export problems
Hi,
I am a beginner using Sql server 2000 with visualstudionet 2003. When I try to export a report to excel spreadsheet. some of the page headers are displaying in separate row. page headers seems to align perfectly with the table columns and they seem fine in preview. Can someone help me with this issue.
Thanks
Bhavya
How are you doing the export ?Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||
I am exporting from Report Manager. Thanks for the resposne.
Bhavya
|||Its hard to tell without having you report design at hand, my suggestion would be to inspect the controls used one by one and eventually create a new report with importing the controls one by one.Jens K. Suessmeyer.
http://www.sqlserver2005.de
Excel export problem
Maybe others have had this similar problem and can give me a hint on how to resolve it...
I have a text box across the top of a report that is causing merged columns when the report is exported to Excel. It's making my users unable to sort the exported table without great difficulty.
What options may I have for putting a title along the top and still now have to worry about the merged columns in Excel?
Thanks much in advance...Troy
I have a text box across the top of a report that is causing merged columns when the report is exported to Excel. It's making my users unable to sort the exported table without great difficulty.
What options may I have for putting a title along the top and still now have to worry about the merged columns in Excel?
Thanks much in advance...Troy
Hello,
Excel renderer will try to preserve the layout of you report. As long as your Title will span multiple table columns (at design time) you will have the problem.
Can you use on single cell for your Title or split it between multiple rows?
Thank you,
Nico
Excel export problem
I have a report that the users want to export to Excel. One of the problems that I am having is that some of the cells in the excel export are renamed as _402, _404, etc. I want them to come in as B22, B24, etc. Any idea why this is happening and how I can stop it?
Joe
The Excel renderer gives unique names to cells that are the operands of formulas. Then, the formulas reference those unique names instead of the cell addresses. This is by design and there is currently no way to export live Excel formulas without using those unique names. That feature is on our list of hopeful features for a future release.
If you want to get rid of formula export entirely and just have the calculated values put into the cells, you can OmitFormulas DeviceInfo parameter:
http://msdn2.microsoft.com/en-us/library/ms159220.aspxBest,
-Chris
|||
OK, I can see that, but how can I affect all Excel exports from the report viewer? Do I set a parameter in the report server config file? Thanks for the info.
Joe
excel export problem
Hi all,
We have a big report with 4 or 5 levels of drill downs and various other
expressions.
While exporting to excel format, unlike other formats, the drill down
capability and other expressions as formulas are also exported. Thus if the
report that is exported is large then exporting does not succeed and excel
throws an error.
"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."
I am using sql server 2005 reporting services sp1. I think this was common
problem and it seems it is not yet fixed. Also I see the answer to this
question as exporting to csv format with ASCII encoding. However, we cannot
use this trick. My question is, is there a way (something like device
information setting or any other property that exists in reporting services)
to prevent drill down information and formulas from reaching excel. however
the font/background color, heading and other stuff, as they appear in pdf
format, should also appear in excel?
is this possible?
Please reply as early as possible.
thanks.Hi,
Formulas can be omitted with "rc:OmitFormulas=True" in the URL. May be you
can use two URL's one with HTML's and the other with Excel as format and
omitting formula's and removing "Action" from the second report so when you
save in excel it removes hyperlink and formulas.
Let me know how you are intend to display from report manager or your
customized code. In the second option we can do it using two URL's.
Amarnath
"msdnuser" wrote:
> Hi all,
> We have a big report with 4 or 5 levels of drill downs and various other
> expressions.
> While exporting to excel format, unlike other formats, the drill down
> capability and other expressions as formulas are also exported. Thus if the
> report that is exported is large then exporting does not succeed and excel
> throws an error.
> "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."
> I am using sql server 2005 reporting services sp1. I think this was common
> problem and it seems it is not yet fixed. Also I see the answer to this
> question as exporting to csv format with ASCII encoding. However, we cannot
> use this trick. My question is, is there a way (something like device
> information setting or any other property that exists in reporting services)
> to prevent drill down information and formulas from reaching excel. however
> the font/background color, heading and other stuff, as they appear in pdf
> format, should also appear in excel?
> is this possible?
> Please reply as early as possible.
> thanks.|||Hi,
Thank you for the reply. Can you tell me how to remove actions for excel
export.
We are using custom webapplication to display the reports.
I tried to render the report in excel format using "url acess" method
applying rc:omitFormula=true. Still I got the same error message. Is there a
way to stop the drill down information from reaching excel? does removing
actions will help this drill down issue too?
Thanks.
"Amarnath" wrote:
> Hi,
> Formulas can be omitted with "rc:OmitFormulas=True" in the URL. May be you
> can use two URL's one with HTML's and the other with Excel as format and
> omitting formula's and removing "Action" from the second report so when you
> save in excel it removes hyperlink and formulas.
> Let me know how you are intend to display from report manager or your
> customized code. In the second option we can do it using two URL's.
> Amarnath
>
> "msdnuser" wrote:
> > Hi all,
> >
> > We have a big report with 4 or 5 levels of drill downs and various other
> > expressions.
> > While exporting to excel format, unlike other formats, the drill down
> > capability and other expressions as formulas are also exported. Thus if the
> > report that is exported is large then exporting does not succeed and excel
> > throws an error.
> >
> > "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."
> >
> > I am using sql server 2005 reporting services sp1. I think this was common
> > problem and it seems it is not yet fixed. Also I see the answer to this
> > question as exporting to csv format with ASCII encoding. However, we cannot
> > use this trick. My question is, is there a way (something like device
> > information setting or any other property that exists in reporting services)
> > to prevent drill down information and formulas from reaching excel. however
> > the font/background color, heading and other stuff, as they appear in pdf
> > format, should also appear in excel?
> > is this possible?
> >
> > Please reply as early as possible.
> >
> > thanks.|||Hi,
If you are using custom there you can do it.
Create a copy of your original report and keep everything same except all
hyperlinks,
e.g report1.RDL, Report_1.RDL.
You can create a hyperlink something like "Export to Excel" when the users
click the link it will be directed to the "copy of the report which you
removed links (Report_1.RDL)"
You should be able to do it with a little bit of coding.
Amarnath
"msdnuser" wrote:
> Hi,
> Thank you for the reply. Can you tell me how to remove actions for excel
> export.
> We are using custom webapplication to display the reports.
> I tried to render the report in excel format using "url acess" method
> applying rc:omitFormula=true. Still I got the same error message. Is there a
> way to stop the drill down information from reaching excel? does removing
> actions will help this drill down issue too?
> Thanks.
> "Amarnath" wrote:
> > Hi,
> > Formulas can be omitted with "rc:OmitFormulas=True" in the URL. May be you
> > can use two URL's one with HTML's and the other with Excel as format and
> > omitting formula's and removing "Action" from the second report so when you
> > save in excel it removes hyperlink and formulas.
> >
> > Let me know how you are intend to display from report manager or your
> > customized code. In the second option we can do it using two URL's.
> >
> > Amarnath
> >
> >
> > "msdnuser" wrote:
> >
> > > Hi all,
> > >
> > > We have a big report with 4 or 5 levels of drill downs and various other
> > > expressions.
> > > While exporting to excel format, unlike other formats, the drill down
> > > capability and other expressions as formulas are also exported. Thus if the
> > > report that is exported is large then exporting does not succeed and excel
> > > throws an error.
> > >
> > > "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."
> > >
> > > I am using sql server 2005 reporting services sp1. I think this was common
> > > problem and it seems it is not yet fixed. Also I see the answer to this
> > > question as exporting to csv format with ASCII encoding. However, we cannot
> > > use this trick. My question is, is there a way (something like device
> > > information setting or any other property that exists in reporting services)
> > > to prevent drill down information and formulas from reaching excel. however
> > > the font/background color, heading and other stuff, as they appear in pdf
> > > format, should also appear in excel?
> > > is this possible?
> > >
> > > Please reply as early as possible.
> > >
> > > thanks.|||Hi ringt,
Thank you for your post and thanks Amarnath's solution.
I would like to know whether the solution from Amarnath is helpful. If the
solution is not match your scenario or you still have further questions or
concern, would you please send the RDL file and the datasource to me? I
understand the information may be sensitive to you, my direct email address
is weilu@.ONLINE.microsoft.com ( Please remove the ONLINE. when you send the
email), you may send the file to me directly and I will keep secure.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Amarnath and Wei Lu,
The solution that Amarnath has given will make the excel export always
expanded. But what we want is something similar to PDF export.
Initially the report will be all collapsed and the user will see this report
in our web application in HTML format. Then user might expand one or two
nodes to any level that he likes. Then user might export to several formats,
one among them is excel.
If he export to excel, then whatever he saw in HTML page before clicking
excel export button should be available/visible in excel report. But there
should not be drilldowns in excel report. Thus only those rows that he saw in
HTML should actually go to Excel like PDF exporting.
Is this possible some how'
Thanks.
"Wei Lu" wrote:
> Hi ringt,
> Thank you for your post and thanks Amarnath's solution.
> I would like to know whether the solution from Amarnath is helpful. If the
> solution is not match your scenario or you still have further questions or
> concern, would you please send the RDL file and the datasource to me? I
> understand the information may be sensitive to you, my direct email address
> is weilu@.ONLINE.microsoft.com ( Please remove the ONLINE. when you send the
> email), you may send the file to me directly and I will keep secure.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi ringt,
Thanks for the update.
I tested on my side and it just works fine. The report is all collapsed and
I expand some node and then export to Excel. It just works as your request
on my side on both SQL Server Reporting Services 2005 and 2000.
Would you please send the rdl file to me for further troubleshoot?
I understand the information may be sensitive to you, my direct email
address is weilu@.ONLINE.microsoft.com (Please remove the ONLINE. when you
send the mail), you may send the file to me directly and I will keep secure.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi,
What you would have tried is normal export to excel. If your report has
drill down and if you expand one or two nodes and export to excel , it is
working good. But what I am saying is it should work the same way but further
expand collapse feature of drill down should not be available in excel export
like PDF. is this possible?
Thanks.
"Wei Lu" wrote:
> Hi ringt,
> Thanks for the update.
> I tested on my side and it just works fine. The report is all collapsed and
> I expand some node and then export to Excel. It just works as your request
> on my side on both SQL Server Reporting Services 2005 and 2000.
> Would you please send the rdl file to me for further troubleshoot?
> I understand the information may be sensitive to you, my direct email
> address is weilu@.ONLINE.microsoft.com (Please remove the ONLINE. when you
> send the mail), you may send the file to me directly and I will keep secure.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi ringt,
Thank you for the update.
I don't think it is possible to excel render works like pdf render since
PDF can not support any operation like expand collapse but excel did
support this operation.
The Excel render will export the collapse and the only thing you could do
is to write a custom render and use this to export your report.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I dont think this can be done. Still its a funny idea, to take "Print screen"
as an image file. "It is as good as what you see is what you get" whether it
is possible you will have to check.
Amarnath.
"Wei Lu" wrote:
> Hi ringt,
> Thank you for the update.
> I don't think it is possible to excel render works like pdf render since
> PDF can not support any operation like expand collapse but excel did
> support this operation.
> The Excel render will export the collapse and the only thing you could do
> is to write a custom render and use this to export your report.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Thank you both for helping me by sharing your knowledge.
"Amarnath" wrote:
> I dont think this can be done. Still its a funny idea, to take "Print screen"
> as an image file. "It is as good as what you see is what you get" whether it
> is possible you will have to check.
> Amarnath.
> "Wei Lu" wrote:
> > Hi ringt,
> >
> > Thank you for the update.
> >
> > I don't think it is possible to excel render works like pdf render since
> > PDF can not support any operation like expand collapse but excel did
> > support this operation.
> >
> > The Excel render will export the collapse and the only thing you could do
> > is to write a custom render and use this to export your report.
> >
> > Sincerely,
> >
> > Wei Lu
> > Microsoft Online Community Support
> >
> > ==================================================> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> >
> > ==================================================> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >|||Hi ringt,
Thank you for the update.
If you have any questions or concerns, please feel free to let me know.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
We have a big report with 4 or 5 levels of drill downs and various other
expressions.
While exporting to excel format, unlike other formats, the drill down
capability and other expressions as formulas are also exported. Thus if the
report that is exported is large then exporting does not succeed and excel
throws an error.
"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."
I am using sql server 2005 reporting services sp1. I think this was common
problem and it seems it is not yet fixed. Also I see the answer to this
question as exporting to csv format with ASCII encoding. However, we cannot
use this trick. My question is, is there a way (something like device
information setting or any other property that exists in reporting services)
to prevent drill down information and formulas from reaching excel. however
the font/background color, heading and other stuff, as they appear in pdf
format, should also appear in excel?
is this possible?
Please reply as early as possible.
thanks.Hi,
Formulas can be omitted with "rc:OmitFormulas=True" in the URL. May be you
can use two URL's one with HTML's and the other with Excel as format and
omitting formula's and removing "Action" from the second report so when you
save in excel it removes hyperlink and formulas.
Let me know how you are intend to display from report manager or your
customized code. In the second option we can do it using two URL's.
Amarnath
"msdnuser" wrote:
> Hi all,
> We have a big report with 4 or 5 levels of drill downs and various other
> expressions.
> While exporting to excel format, unlike other formats, the drill down
> capability and other expressions as formulas are also exported. Thus if the
> report that is exported is large then exporting does not succeed and excel
> throws an error.
> "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."
> I am using sql server 2005 reporting services sp1. I think this was common
> problem and it seems it is not yet fixed. Also I see the answer to this
> question as exporting to csv format with ASCII encoding. However, we cannot
> use this trick. My question is, is there a way (something like device
> information setting or any other property that exists in reporting services)
> to prevent drill down information and formulas from reaching excel. however
> the font/background color, heading and other stuff, as they appear in pdf
> format, should also appear in excel?
> is this possible?
> Please reply as early as possible.
> thanks.|||Hi,
Thank you for the reply. Can you tell me how to remove actions for excel
export.
We are using custom webapplication to display the reports.
I tried to render the report in excel format using "url acess" method
applying rc:omitFormula=true. Still I got the same error message. Is there a
way to stop the drill down information from reaching excel? does removing
actions will help this drill down issue too?
Thanks.
"Amarnath" wrote:
> Hi,
> Formulas can be omitted with "rc:OmitFormulas=True" in the URL. May be you
> can use two URL's one with HTML's and the other with Excel as format and
> omitting formula's and removing "Action" from the second report so when you
> save in excel it removes hyperlink and formulas.
> Let me know how you are intend to display from report manager or your
> customized code. In the second option we can do it using two URL's.
> Amarnath
>
> "msdnuser" wrote:
> > Hi all,
> >
> > We have a big report with 4 or 5 levels of drill downs and various other
> > expressions.
> > While exporting to excel format, unlike other formats, the drill down
> > capability and other expressions as formulas are also exported. Thus if the
> > report that is exported is large then exporting does not succeed and excel
> > throws an error.
> >
> > "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."
> >
> > I am using sql server 2005 reporting services sp1. I think this was common
> > problem and it seems it is not yet fixed. Also I see the answer to this
> > question as exporting to csv format with ASCII encoding. However, we cannot
> > use this trick. My question is, is there a way (something like device
> > information setting or any other property that exists in reporting services)
> > to prevent drill down information and formulas from reaching excel. however
> > the font/background color, heading and other stuff, as they appear in pdf
> > format, should also appear in excel?
> > is this possible?
> >
> > Please reply as early as possible.
> >
> > thanks.|||Hi,
If you are using custom there you can do it.
Create a copy of your original report and keep everything same except all
hyperlinks,
e.g report1.RDL, Report_1.RDL.
You can create a hyperlink something like "Export to Excel" when the users
click the link it will be directed to the "copy of the report which you
removed links (Report_1.RDL)"
You should be able to do it with a little bit of coding.
Amarnath
"msdnuser" wrote:
> Hi,
> Thank you for the reply. Can you tell me how to remove actions for excel
> export.
> We are using custom webapplication to display the reports.
> I tried to render the report in excel format using "url acess" method
> applying rc:omitFormula=true. Still I got the same error message. Is there a
> way to stop the drill down information from reaching excel? does removing
> actions will help this drill down issue too?
> Thanks.
> "Amarnath" wrote:
> > Hi,
> > Formulas can be omitted with "rc:OmitFormulas=True" in the URL. May be you
> > can use two URL's one with HTML's and the other with Excel as format and
> > omitting formula's and removing "Action" from the second report so when you
> > save in excel it removes hyperlink and formulas.
> >
> > Let me know how you are intend to display from report manager or your
> > customized code. In the second option we can do it using two URL's.
> >
> > Amarnath
> >
> >
> > "msdnuser" wrote:
> >
> > > Hi all,
> > >
> > > We have a big report with 4 or 5 levels of drill downs and various other
> > > expressions.
> > > While exporting to excel format, unlike other formats, the drill down
> > > capability and other expressions as formulas are also exported. Thus if the
> > > report that is exported is large then exporting does not succeed and excel
> > > throws an error.
> > >
> > > "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."
> > >
> > > I am using sql server 2005 reporting services sp1. I think this was common
> > > problem and it seems it is not yet fixed. Also I see the answer to this
> > > question as exporting to csv format with ASCII encoding. However, we cannot
> > > use this trick. My question is, is there a way (something like device
> > > information setting or any other property that exists in reporting services)
> > > to prevent drill down information and formulas from reaching excel. however
> > > the font/background color, heading and other stuff, as they appear in pdf
> > > format, should also appear in excel?
> > > is this possible?
> > >
> > > Please reply as early as possible.
> > >
> > > thanks.|||Hi ringt,
Thank you for your post and thanks Amarnath's solution.
I would like to know whether the solution from Amarnath is helpful. If the
solution is not match your scenario or you still have further questions or
concern, would you please send the RDL file and the datasource to me? I
understand the information may be sensitive to you, my direct email address
is weilu@.ONLINE.microsoft.com ( Please remove the ONLINE. when you send the
email), you may send the file to me directly and I will keep secure.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Amarnath and Wei Lu,
The solution that Amarnath has given will make the excel export always
expanded. But what we want is something similar to PDF export.
Initially the report will be all collapsed and the user will see this report
in our web application in HTML format. Then user might expand one or two
nodes to any level that he likes. Then user might export to several formats,
one among them is excel.
If he export to excel, then whatever he saw in HTML page before clicking
excel export button should be available/visible in excel report. But there
should not be drilldowns in excel report. Thus only those rows that he saw in
HTML should actually go to Excel like PDF exporting.
Is this possible some how'
Thanks.
"Wei Lu" wrote:
> Hi ringt,
> Thank you for your post and thanks Amarnath's solution.
> I would like to know whether the solution from Amarnath is helpful. If the
> solution is not match your scenario or you still have further questions or
> concern, would you please send the RDL file and the datasource to me? I
> understand the information may be sensitive to you, my direct email address
> is weilu@.ONLINE.microsoft.com ( Please remove the ONLINE. when you send the
> email), you may send the file to me directly and I will keep secure.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi ringt,
Thanks for the update.
I tested on my side and it just works fine. The report is all collapsed and
I expand some node and then export to Excel. It just works as your request
on my side on both SQL Server Reporting Services 2005 and 2000.
Would you please send the rdl file to me for further troubleshoot?
I understand the information may be sensitive to you, my direct email
address is weilu@.ONLINE.microsoft.com (Please remove the ONLINE. when you
send the mail), you may send the file to me directly and I will keep secure.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi,
What you would have tried is normal export to excel. If your report has
drill down and if you expand one or two nodes and export to excel , it is
working good. But what I am saying is it should work the same way but further
expand collapse feature of drill down should not be available in excel export
like PDF. is this possible?
Thanks.
"Wei Lu" wrote:
> Hi ringt,
> Thanks for the update.
> I tested on my side and it just works fine. The report is all collapsed and
> I expand some node and then export to Excel. It just works as your request
> on my side on both SQL Server Reporting Services 2005 and 2000.
> Would you please send the rdl file to me for further troubleshoot?
> I understand the information may be sensitive to you, my direct email
> address is weilu@.ONLINE.microsoft.com (Please remove the ONLINE. when you
> send the mail), you may send the file to me directly and I will keep secure.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi ringt,
Thank you for the update.
I don't think it is possible to excel render works like pdf render since
PDF can not support any operation like expand collapse but excel did
support this operation.
The Excel render will export the collapse and the only thing you could do
is to write a custom render and use this to export your report.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I dont think this can be done. Still its a funny idea, to take "Print screen"
as an image file. "It is as good as what you see is what you get" whether it
is possible you will have to check.
Amarnath.
"Wei Lu" wrote:
> Hi ringt,
> Thank you for the update.
> I don't think it is possible to excel render works like pdf render since
> PDF can not support any operation like expand collapse but excel did
> support this operation.
> The Excel render will export the collapse and the only thing you could do
> is to write a custom render and use this to export your report.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Thank you both for helping me by sharing your knowledge.
"Amarnath" wrote:
> I dont think this can be done. Still its a funny idea, to take "Print screen"
> as an image file. "It is as good as what you see is what you get" whether it
> is possible you will have to check.
> Amarnath.
> "Wei Lu" wrote:
> > Hi ringt,
> >
> > Thank you for the update.
> >
> > I don't think it is possible to excel render works like pdf render since
> > PDF can not support any operation like expand collapse but excel did
> > support this operation.
> >
> > The Excel render will export the collapse and the only thing you could do
> > is to write a custom render and use this to export your report.
> >
> > Sincerely,
> >
> > Wei Lu
> > Microsoft Online Community Support
> >
> > ==================================================> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> >
> > ==================================================> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >|||Hi ringt,
Thank you for the update.
If you have any questions or concerns, please feel free to let me know.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
excel export not showing client name in heading
I am putting the client name in my header using ReportItems! reference to
textbox in report - this renders correctly on my server and in pdf however in
excel the client name is not showing up on the report. There are 2 textboxes
overlapping each other because I have 2 groups and when the page spans the
client name will come from the alt text box. I have tried NOT overlapping
them and the result is the same - neither one displays on the export to excel.This is common. In RS 2000, the pdf rendering extension didn't do it...
What you have to do to work around it is use rectangles and textboxes to
simulate a page header OR you can pass it in as a parameter.
-Tim
"MJT" <MJT@.discussions.microsoft.com> wrote in message
news:365BECF1-AD51-42E0-BF79-DE9011DC166C@.microsoft.com...
>I am putting the client name in my header using ReportItems! reference to
> textbox in report - this renders correctly on my server and in pdf however
> in
> excel the client name is not showing up on the report. There are 2
> textboxes
> overlapping each other because I have 2 groups and when the page spans the
> client name will come from the alt text box. I have tried NOT overlapping
> them and the result is the same - neither one displays on the export to
> excel.|||Thanks Tim,
Cant pass as a parm as they use client code (not the same) for the parm
and takes too long to run if I make it a report parm (since it cant be a
query parm I am using a stored procedure). I noticed your post about putting
this info not in a page heading but in a rectangle and hiding/showing which
might be an option if hiding/showing didnt leave white space when hidden (big
problem). Seems like such a simple basic thing that should work, doesnt it?
I mean ... who *doesnt* need data information in their heading'
"Tim Dot NoSpam" wrote:
> This is common. In RS 2000, the pdf rendering extension didn't do it...
> What you have to do to work around it is use rectangles and textboxes to
> simulate a page header OR you can pass it in as a parameter.
> -Tim
> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> news:365BECF1-AD51-42E0-BF79-DE9011DC166C@.microsoft.com...
> >I am putting the client name in my header using ReportItems! reference to
> > textbox in report - this renders correctly on my server and in pdf however
> > in
> > excel the client name is not showing up on the report. There are 2
> > textboxes
> > overlapping each other because I have 2 groups and when the page spans the
> > client name will come from the alt text box. I have tried NOT overlapping
> > them and the result is the same - neither one displays on the export to
> > excel.
>
>|||Hi
Can to tell me to Hide or disable page Header while exporting to Excel format.
calvin
"MJT" wrote:
> I am putting the client name in my header using ReportItems! reference to
> textbox in report - this renders correctly on my server and in pdf however in
> excel the client name is not showing up on the report. There are 2 textboxes
> overlapping each other because I have 2 groups and when the page spans the
> client name will come from the alt text box. I have tried NOT overlapping
> them and the result is the same - neither one displays on the export to excel.|||Hi
I want to export a report to excel format, but in excel the page header
should not come. Can u please help how to slove this.
Calvin
"Tim Dot NoSpam" wrote:
> This is common. In RS 2000, the pdf rendering extension didn't do it...
> What you have to do to work around it is use rectangles and textboxes to
> simulate a page header OR you can pass it in as a parameter.
> -Tim
> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> news:365BECF1-AD51-42E0-BF79-DE9011DC166C@.microsoft.com...
> >I am putting the client name in my header using ReportItems! reference to
> > textbox in report - this renders correctly on my server and in pdf however
> > in
> > excel the client name is not showing up on the report. There are 2
> > textboxes
> > overlapping each other because I have 2 groups and when the page spans the
> > client name will come from the alt text box. I have tried NOT overlapping
> > them and the result is the same - neither one displays on the export to
> > excel.
>
>
textbox in report - this renders correctly on my server and in pdf however in
excel the client name is not showing up on the report. There are 2 textboxes
overlapping each other because I have 2 groups and when the page spans the
client name will come from the alt text box. I have tried NOT overlapping
them and the result is the same - neither one displays on the export to excel.This is common. In RS 2000, the pdf rendering extension didn't do it...
What you have to do to work around it is use rectangles and textboxes to
simulate a page header OR you can pass it in as a parameter.
-Tim
"MJT" <MJT@.discussions.microsoft.com> wrote in message
news:365BECF1-AD51-42E0-BF79-DE9011DC166C@.microsoft.com...
>I am putting the client name in my header using ReportItems! reference to
> textbox in report - this renders correctly on my server and in pdf however
> in
> excel the client name is not showing up on the report. There are 2
> textboxes
> overlapping each other because I have 2 groups and when the page spans the
> client name will come from the alt text box. I have tried NOT overlapping
> them and the result is the same - neither one displays on the export to
> excel.|||Thanks Tim,
Cant pass as a parm as they use client code (not the same) for the parm
and takes too long to run if I make it a report parm (since it cant be a
query parm I am using a stored procedure). I noticed your post about putting
this info not in a page heading but in a rectangle and hiding/showing which
might be an option if hiding/showing didnt leave white space when hidden (big
problem). Seems like such a simple basic thing that should work, doesnt it?
I mean ... who *doesnt* need data information in their heading'
"Tim Dot NoSpam" wrote:
> This is common. In RS 2000, the pdf rendering extension didn't do it...
> What you have to do to work around it is use rectangles and textboxes to
> simulate a page header OR you can pass it in as a parameter.
> -Tim
> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> news:365BECF1-AD51-42E0-BF79-DE9011DC166C@.microsoft.com...
> >I am putting the client name in my header using ReportItems! reference to
> > textbox in report - this renders correctly on my server and in pdf however
> > in
> > excel the client name is not showing up on the report. There are 2
> > textboxes
> > overlapping each other because I have 2 groups and when the page spans the
> > client name will come from the alt text box. I have tried NOT overlapping
> > them and the result is the same - neither one displays on the export to
> > excel.
>
>|||Hi
Can to tell me to Hide or disable page Header while exporting to Excel format.
calvin
"MJT" wrote:
> I am putting the client name in my header using ReportItems! reference to
> textbox in report - this renders correctly on my server and in pdf however in
> excel the client name is not showing up on the report. There are 2 textboxes
> overlapping each other because I have 2 groups and when the page spans the
> client name will come from the alt text box. I have tried NOT overlapping
> them and the result is the same - neither one displays on the export to excel.|||Hi
I want to export a report to excel format, but in excel the page header
should not come. Can u please help how to slove this.
Calvin
"Tim Dot NoSpam" wrote:
> This is common. In RS 2000, the pdf rendering extension didn't do it...
> What you have to do to work around it is use rectangles and textboxes to
> simulate a page header OR you can pass it in as a parameter.
> -Tim
> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> news:365BECF1-AD51-42E0-BF79-DE9011DC166C@.microsoft.com...
> >I am putting the client name in my header using ReportItems! reference to
> > textbox in report - this renders correctly on my server and in pdf however
> > in
> > excel the client name is not showing up on the report. There are 2
> > textboxes
> > overlapping each other because I have 2 groups and when the page spans the
> > client name will come from the alt text box. I have tried NOT overlapping
> > them and the result is the same - neither one displays on the export to
> > excel.
>
>
Excel export missing table header
I am working with RS2000 SP2 and VS2003.
I have a simple report with just one table, two levels of grouping with subtotals and a table header. There is also a separate page header. The report renders correctly on screen and when printed.
When I export the report in Excel format the detail lines, group sub-totals and page head appear. However, the problem I have is that the table header is not shown. So the user can't make out what data is shown each column. How can I get the table header to appear when exporting to Excel?
TIA, Magendo_man
To complicate matters further, I have added another table to this report, which is a copy of the original one. This table uses the same dataset but is filtered and sorted differently, with no grouping and a footer total. I set the table to have a page break before it is printed.
Now when I export to Excel I get the same problem with missing table header for the first table, but I do get the table header for this second table.
TIA, Magendo_man
Excel Export Large File Size
When I export a matrix report to Excel (65 rows by 228 columns, about 15000
cells) the file size exceeds 15mb.
As the Excel file is sent out daily as an e-mail attachment in an SRSS
subscription I receive a lot of complaints about this.
Other export formats for the same report such as Web archive are tiny, but
the subscribers insist on Excel.
I have applied the latest service packs to SQL Server 2005.
Any tips/workarounds would be appreciated.
Regards
Ian OlsenOn Mar 22, 7:47 am, Wrighty <wrig...@.donotspam.com> wrote:
> When I export a matrix report to Excel (65 rows by 228 columns, about 15000
> cells) the file size exceeds 15mb.
> As the Excel file is sent out daily as an e-mail attachment in an SRSS
> subscription I receive a lot of complaints about this.
> Other export formats for the same report such as Web archive are tiny, but
> the subscribers insist on Excel.
> I have applied the latest service packs to SQL Server 2005.
> Any tips/workarounds would be appreciated.
> Regards
> Ian Olsen
The only other options are to use a compression tool to zip the file
before sending it (most likely, not a snapshot option, but a custom
one) or to export to CSV instead (which might save a little file size
but you loose formatting). The only other thing would be to have the
users save a web archive, etc as an excel file. Hope this helps.
Regards,
Enrique Martinez
Sr. SQL Server Developer
cells) the file size exceeds 15mb.
As the Excel file is sent out daily as an e-mail attachment in an SRSS
subscription I receive a lot of complaints about this.
Other export formats for the same report such as Web archive are tiny, but
the subscribers insist on Excel.
I have applied the latest service packs to SQL Server 2005.
Any tips/workarounds would be appreciated.
Regards
Ian OlsenOn Mar 22, 7:47 am, Wrighty <wrig...@.donotspam.com> wrote:
> When I export a matrix report to Excel (65 rows by 228 columns, about 15000
> cells) the file size exceeds 15mb.
> As the Excel file is sent out daily as an e-mail attachment in an SRSS
> subscription I receive a lot of complaints about this.
> Other export formats for the same report such as Web archive are tiny, but
> the subscribers insist on Excel.
> I have applied the latest service packs to SQL Server 2005.
> Any tips/workarounds would be appreciated.
> Regards
> Ian Olsen
The only other options are to use a compression tool to zip the file
before sending it (most likely, not a snapshot option, but a custom
one) or to export to CSV instead (which might save a little file size
but you loose formatting). The only other thing would be to have the
users save a web archive, etc as an excel file. Hope this helps.
Regards,
Enrique Martinez
Sr. SQL Server Developer
Excel Export formatting problem
When i export my report to excel , i see extra empty rows between data rows .What might cause that?Does anyone have an idea?What do you mean by extra rows? Do you mean blank rows?|||Yes,blank row are involved...|||Do you get blank rows between data or at the end?|||i get blank rows between data rows (between every one of them)|||Do you see blank rows in preview mode of the report?|||Not in preview mode , when i export the report to excel ,i see blank rows in excel sheet|||It may the problem in EXCEL. Try to increase the width of the cells|||Thanx,i will try
excel export footer is a literal?
When a report is exported to Excel, the footer is set to a literal "page 1 of 1" even though it's specified as
="Page " + CStr(Globals!PageNumber) + " of " + CStr(Globals!TotalPages)
in the rldc report definition.
Hence, if you print from Excel every page has the 'page 1 of 1' footer. Not very useful.
Is there a way to either suppress the output of the footer (only when going to Excel cause you need it when exporting to PDF) -or- get it to generate the correct excel footer of 'page 1 of ?'?
Thanks,
Answer...
The above expression works but is wrong! The '&' should be used since this is VB syntax.
Changing the expression to
="Page " & Globals!PageNumber & " of " & Globals!TotalPages
fixes the problem!
Subscribe to:
Posts (Atom)