Excel export missing last row

Hi,
I have a some reports render in html but the last row would always be
missing when export to Excel. However, if I change the parameter and
get a different version to export, then the last row would appear.
Do you guys have any idea what is going on? A bug maybe?
Thanks
EugeneI'm having the same problem. Have you been able to resolve this?
"Eugene" wrote:
> Hi,
> I have a some reports render in html but the last row would always be
> missing when export to Excel. However, if I change the parameter and
> get a different version to export, then the last row would appear.
> Do you guys have any idea what is going on? A bug maybe?
> Thanks
> Eugene
>

excel export /collapsed fails to render excel file

Trying to render a report that has three groups two expand and collapse and
have charts. The first attempts to render were successful but all later ones
fail. And excel produces the following message:
Microsoft Office Excel File Repair Log
Errors were detected in file 'C:\Documents and Settings\johnsond\Local
Settings\Temporary Internet
Files\Content.IE5\UT38LWFQ\CustomerSalesByPartType[2].xls'
The following is a list of repairs:
Damage to the file was so extensive that repairs were not possible. Excel
attempted to recover your formulas and values, but some data may have been
lost or corrupted.
Can anyone help with this?DJJIII,
I wish I were writing with a solution (as I also am getting the annonying
"damage too extensive" message in excel.) I have an MSDN subscription, so we
should get a MS reply. I will repost under the subject: "Damage to file
message when exporting to excel" for good measure.
The interesting thing in my case is that I have a fairly complex report with
many charts and tables. My "top level" report throws this excel error.
However, if I add parameters ("drill down report") the structure of the
report is exactly the same with charts and tables, just less (or different)
data and then it renders fine. I am not using groups at all, so I don't
think the issue is directly related to your use of groups.
My guess is there is some data-related issue as our same report (both
top-level and drilldown) with different data works fine.
Our report actually is a collection of 10 or so subreports, so I will be
doing a little debugging by removing subreports to see if I can identify the
subreport or data that is causing the issue.
-David
"DJJIII" wrote:
> Trying to render a report that has three groups two expand and collapse and
> have charts. The first attempts to render were successful but all later ones
> fail. And excel produces the following message:
> Microsoft Office Excel File Repair Log
> Errors were detected in file 'C:\Documents and Settings\johnsond\Local
> Settings\Temporary Internet
> Files\Content.IE5\UT38LWFQ\CustomerSalesByPartType[2].xls'
> The following is a list of repairs:
> Damage to the file was so extensive that repairs were not possible. Excel
> attempted to recover your formulas and values, but some data may have been
> lost or corrupted.
> Can anyone help with this?
>

Excel export

Hello,
I am having a problem when exporting a report to Excel. I am using the
SQL RS web service to render a report.
It seems that the report is always rendered using parameters default
values. It is not using parameters that i pass to the service. I am
having this problem only when rendering in Excel format. PDF is
working ok.
Anyone already seen that problem?
using SQL RS with SP1
ThanksWhat are the execution options for your report? If you've configured the
report execution options to be 'snapshot' then you cannot alter the values
of any parameters that affect the query after the snapshot has been taken.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
"Renaud Langis" <rlangis@.sympatico.ca> wrote in message
news:l273g0lrcb8ao5ibu0du8rcvnhlbfuvi5v@.4ax.com...
> Hello,
> I am having a problem when exporting a report to Excel. I am using the
> SQL RS web service to render a report.
> It seems that the report is always rendered using parameters default
> values. It is not using parameters that i pass to the service. I am
> having this problem only when rendering in Excel format. PDF is
> working ok.
> Anyone already seen that problem?
> using SQL RS with SP1
> Thanks|||i am using the web service through ServerXmlHttp. with command =Render.
It is working well when exporting to pdf.
On Mon, 26 Jul 2004 14:39:58 -0700, "Lukasz Pawlowski [MSFT]"
<lukaszp@.online.microsoft.com> wrote:
>What are the execution options for your report? If you've configured the
>report execution options to be 'snapshot' then you cannot alter the values
>of any parameters that affect the query after the snapshot has been taken.
>-Lukasz

Excel Device Information Setting

How do I pass Device Information Settings when exporting a report to Excel?
The documentation explains how to do this by URL, and by using the Render
method, but I would like to continue to use the Export link on the default
toolbar. I need to specify the RemoveSpace setting - I'm hoping this will
eliminate the zero-width empty columns in the Excel spreadsheet inserted
caused by having a textbox in the page header.
According to the documentation, the RemoveSpace device setting should be
.125 by default, and any columns with no data and a width less than this
threshold should be removed by default. However, when I export to Excel
empty columns are inserted.
Thanks
BillI am very interested if you have found how to do this. I am trying to pass to
RemoveSpace device info throught the URL like this "rc:RemoveSpace=0.5in"
(this is of course a part of a larger URL). But I can't get this to work. Has
also tried to set this up in the configurations files, but has not succeed.
"bill" wrote:
> How do I pass Device Information Settings when exporting a report to Excel?
> The documentation explains how to do this by URL, and by using the Render
> method, but I would like to continue to use the Export link on the default
> toolbar. I need to specify the RemoveSpace setting - I'm hoping this will
> eliminate the zero-width empty columns in the Excel spreadsheet inserted
> caused by having a textbox in the page header.
> According to the documentation, the RemoveSpace device setting should be
> ..125 by default, and any columns with no data and a width less than this
> threshold should be removed by default. However, when I export to Excel
> empty columns are inserted.
> Thanks
> Bill
>
>

Excel Coloring export and SP1

I currently have several formulas to change the background or text coloring
based on values in a report. All format render correctly except excel on out
put. If I have a column that changes to red when there is a negative value,
all numbers end up red in that column when exported to excel.
Is anyone else having this problem with SP1? Is there a work around or is
this a but? If it is a but is it fixed in SP2?
(I have asked users just to print to other formats but the are using the
excel data in excel)
ThanksTom,
This was an error I came across in SP1 quite some time ago, I think it
affects matrices, it was some time ago, I can't remember whether I told
Microsoft or not. We've been discouraging users from exporting to excel
which is why I haven't hit the problem again anyway.
I have SP2 Beta and will try it out for you later today. If it's an
error there I'll raise a bug log with MS.
Chris
Tom wrote:
> I currently have several formulas to change the background or text
> coloring based on values in a report. All format render correctly
> except excel on out put. If I have a column that changes to red when
> there is a negative value, all numbers end up red in that column when
> exported to excel.
> Is anyone else having this problem with SP1? Is there a work around
> or is this a but? If it is a but is it fixed in SP2?
> (I have asked users just to print to other formats but the are using
> the excel data in excel)
> Thanks|||Chris,
Any word on this if it is fixed in SP2? Is it still an open issue?
Thanks
Tom
"Chris McGuigan" wrote:
> Tom,
> This was an error I came across in SP1 quite some time ago, I think it
> affects matrices, it was some time ago, I can't remember whether I told
> Microsoft or not. We've been discouraging users from exporting to excel
> which is why I haven't hit the problem again anyway.
> I have SP2 Beta and will try it out for you later today. If it's an
> error there I'll raise a bug log with MS.
> Chris
>
> Tom wrote:
> > I currently have several formulas to change the background or text
> > coloring based on values in a report. All format render correctly
> > except excel on out put. If I have a column that changes to red when
> > there is a negative value, all numbers end up red in that column when
> > exported to excel.
> >
> > Is anyone else having this problem with SP1? Is there a work around
> > or is this a but? If it is a but is it fixed in SP2?
> >
> > (I have asked users just to print to other formats but the are using
> > the excel data in excel)
> >
> > Thanks
>

Exceeding Excel Row Limit

We have a report that returns more than 65,000 rows that we need to render to
Excel. Is there a way to make RS parse the data into multiple worksheets, or
will we need to split the data into more than one report for rendering?I don't know the answer to your question, but why do you have such a
large report anyway? You're not the only one with such a monster, so
there must be some reason for it.. however I cannot think what it might
be. Please help me understand this...|||Good question! First of all (and probably most importantly), the users of
this report are very fond of Excel, and what the users want, the users get!
Secondly, these reports deal with telephone number data. It is common for a
user to need a list of all telephone numbers owned by a customer (filtered by
certain criteria, as all numbers can easily number in the hundreds of
thousands) in a format that is easily understood and comforting.
Aileen
"timseal" wrote:
> I don't know the answer to your question, but why do you have such a
> large report anyway? You're not the only one with such a monster, so
> there must be some reason for it.. however I cannot think what it might
> be. Please help me understand this...
>|||No, there is no way to do this. Plus, you are better off to not export as
Excel but to export as CSV. The current export uses Unicode which Excel
doesn't know how to handle. So I put in a link and use jump to URL.
Here is an example of a Jump to URL link I use. This causes Excel to come up
with the data in a separate window:
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
"&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
Very nice and very fast.
If there is some way to split up the numbers then have a report with no
data, just several textboxes which link to a subset of the data (which will
be less than 65,000).
Also, I think that the most recent Excel takes more than 65,000 rows.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Aileen" <Aileen@.discussions.microsoft.com> wrote in message
news:AFA747C3-F913-490B-BD88-E78284B30E27@.microsoft.com...
> We have a report that returns more than 65,000 rows that we need to render
> to
> Excel. Is there a way to make RS parse the data into multiple worksheets,
> or
> will we need to split the data into more than one report for rendering?
>|||XL 2003 takes 65,536 rows. No way to simply put > 65k rows in another
worksheet? Using a .csv really doesn't do much, since .csv is typically
registered to XL anyway, so clicking it to open will cause it to try to load
into XL.
regards
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:OCiLzuenFHA.3288@.TK2MSFTNGP09.phx.gbl...
> No, there is no way to do this. Plus, you are better off to not export as
> Excel but to export as CSV. The current export uses Unicode which Excel
> doesn't know how to handle. So I put in a link and use jump to URL.
> Here is an example of a Jump to URL link I use. This causes Excel to come
> up with the data in a separate window:
> ="javascript:void(window.open('" & Globals!ReportServerUrl &
> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
> Very nice and very fast.
> If there is some way to split up the numbers then have a report with no
> data, just several textboxes which link to a subset of the data (which
> will be less than 65,000).
> Also, I think that the most recent Excel takes more than 65,000 rows.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
>
> "Aileen" <Aileen@.discussions.microsoft.com> wrote in message
> news:AFA747C3-F913-490B-BD88-E78284B30E27@.microsoft.com...
>> We have a report that returns more than 65,000 rows that we need to
>> render to
>> Excel. Is there a way to make RS parse the data into multiple
>> worksheets, or
>> will we need to split the data into more than one report for rendering?
>|||The CSV format is out, the users aren't comfortable with that. Good to know
about the jump to URL, we'll use that. Also, the idea to divide the data is
one we were considering if we couldn't just dump all data at once, we'll
probably go with that.
Thank you.
"Bruce L-C [MVP]" wrote:
> No, there is no way to do this. Plus, you are better off to not export as
> Excel but to export as CSV. The current export uses Unicode which Excel
> doesn't know how to handle. So I put in a link and use jump to URL.
> Here is an example of a Jump to URL link I use. This causes Excel to come up
> with the data in a separate window:
> ="javascript:void(window.open('" & Globals!ReportServerUrl &
> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
> Very nice and very fast.
> If there is some way to split up the numbers then have a report with no
> data, just several textboxes which link to a subset of the data (which will
> be less than 65,000).
> Also, I think that the most recent Excel takes more than 65,000 rows.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services|||This is transparent to the user. You do a jump to URL using CSV ASCII and it
comes right up in an Excel worksheet. They don't have to do anything. As far
as the users know it is Excel.
Have you tried exporting as Excel versus CSV? We are talking probably an
order of magnitude difference in speed (or more). Depending on what you are
doing it can make the difference between it being usable and not. When you
do CSV as an export and it does it as unicode it puts all the data in one
column. When you do it as CSV ASCII the sheet comes right up.
Even very simple data will take a very long time for 65,000 rows. I suggest
you do some timing to see what I am talking about.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Aileen" <Aileen@.discussions.microsoft.com> wrote in message
news:CEDC0BEE-F67F-4BD3-A87F-117F9F8C0074@.microsoft.com...
> The CSV format is out, the users aren't comfortable with that. Good to
> know
> about the jump to URL, we'll use that. Also, the idea to divide the data
> is
> one we were considering if we couldn't just dump all data at once, we'll
> probably go with that.
> Thank you.
>
> "Bruce L-C [MVP]" wrote:
>> No, there is no way to do this. Plus, you are better off to not export as
>> Excel but to export as CSV. The current export uses Unicode which Excel
>> doesn't know how to handle. So I put in a link and use jump to URL.
>> Here is an example of a Jump to URL link I use. This causes Excel to come
>> up
>> with the data in a separate window:
>> ="javascript:void(window.open('" & Globals!ReportServerUrl &
>> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
>> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>> Very nice and very fast.
>> If there is some way to split up the numbers then have a report with no
>> data, just several textboxes which link to a subset of the data (which
>> will
>> be less than 65,000).
>> Also, I think that the most recent Excel takes more than 65,000 rows.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services|||That is the point (that CSV is registered to Excel). I want Excel to come up
with the CSV data. I just want it to come up fast when there is lots of
data.
And no, there is no way to sell it to put the additional rows into another
spreadsheet.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Kizzy" <kizzy@.azstarnet.com> wrote in message
news:%23RyCDzenFHA.3936@.TK2MSFTNGP10.phx.gbl...
> XL 2003 takes 65,536 rows. No way to simply put > 65k rows in another
> worksheet? Using a .csv really doesn't do much, since .csv is typically
> registered to XL anyway, so clicking it to open will cause it to try to
> load into XL.
> regards
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:OCiLzuenFHA.3288@.TK2MSFTNGP09.phx.gbl...
>> No, there is no way to do this. Plus, you are better off to not export as
>> Excel but to export as CSV. The current export uses Unicode which Excel
>> doesn't know how to handle. So I put in a link and use jump to URL.
>> Here is an example of a Jump to URL link I use. This causes Excel to come
>> up with the data in a separate window:
>> ="javascript:void(window.open('" & Globals!ReportServerUrl &
>> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
>> "&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
>> Very nice and very fast.
>> If there is some way to split up the numbers then have a report with no
>> data, just several textboxes which link to a subset of the data (which
>> will be less than 65,000).
>> Also, I think that the most recent Excel takes more than 65,000 rows.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>>
>> "Aileen" <Aileen@.discussions.microsoft.com> wrote in message
>> news:AFA747C3-F913-490B-BD88-E78284B30E27@.microsoft.com...
>> We have a report that returns more than 65,000 rows that we need to
>> render to
>> Excel. Is there a way to make RS parse the data into multiple
>> worksheets, or
>> will we need to split the data into more than one report for rendering?
>>
>|||Personally, I would find a telephone directory search application to be
more comforting. Cheaper and easier for all concerned. I bet you
could have photocopied it all by now, but that's a ridiculous idea,
isn't it?|||I realize it comes up in Excel, but I haven't tried exporting using CSV as I
assumed it would have the same problem (and the users tend to freak over
minor issues and the .csv extention might trouble them). Definitely good to
know, I'll see if that will work for us.
Thanks again.
"Bruce L-C [MVP]" wrote:
> This is transparent to the user. You do a jump to URL using CSV ASCII and it
> comes right up in an Excel worksheet. They don't have to do anything. As far
> as the users know it is Excel.
> Have you tried exporting as Excel versus CSV? We are talking probably an
> order of magnitude difference in speed (or more). Depending on what you are
> doing it can make the difference between it being usable and not. When you
> do CSV as an export and it does it as unicode it puts all the data in one
> column. When you do it as CSV ASCII the sheet comes right up.
> Even very simple data will take a very long time for 65,000 rows. I suggest
> you do some timing to see what I am talking about.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services|||We do have an application with search functionality. Unfortunately the
searching process would frequently kill our application server due to the
volume involved, which is why we went to RS in the first place - we could
move the straight search/view to another server and leave the app available
for its intended purpose, which is editing the telephone number data.
"timseal" wrote:
> Personally, I would find a telephone directory search application to be
> more comforting. Cheaper and easier for all concerned. I bet you
> could have photocopied it all by now, but that's a ridiculous idea,
> isn't it?|||If you can group the data in a way that will put a limit of lines per group
you can then break the report up into multiple worksheets.
First put the grouping on and the put a page break at the end of the group
and it will split the data onto different worksheets.
"Aileen" wrote:
> I realize it comes up in Excel, but I haven't tried exporting using CSV as I
> assumed it would have the same problem (and the users tend to freak over
> minor issues and the .csv extention might trouble them). Definitely good to
> know, I'll see if that will work for us.
> Thanks again.
> "Bruce L-C [MVP]" wrote:
> > This is transparent to the user. You do a jump to URL using CSV ASCII and it
> > comes right up in an Excel worksheet. They don't have to do anything. As far
> > as the users know it is Excel.
> >
> > Have you tried exporting as Excel versus CSV? We are talking probably an
> > order of magnitude difference in speed (or more). Depending on what you are
> > doing it can make the difference between it being usable and not. When you
> > do CSV as an export and it does it as unicode it puts all the data in one
> > column. When you do it as CSV ASCII the sheet comes right up.
> >
> > Even very simple data will take a very long time for 65,000 rows. I suggest
> > you do some timing to see what I am talking about.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
>|||I ran into same problem this what I did to fix:
In the data I found something to group the data on. In my case it was Month.
Edit the new group and put a page break after or before the group. This will
Force a new page and when converted to excel it will put that month in its
own tab.
In you case You may be able to do location or department.
Hope this helps.
"Aileen" wrote:
> We have a report that returns more than 65,000 rows that we need to render to
> Excel. Is there a way to make RS parse the data into multiple worksheets, or
> will we need to split the data into more than one report for rendering?
>|||how about adding a page break?
"jc82196" <jc82196@.discussions.microsoft.com> wrote in message
news:05B1206C-7C90-42D7-B8F2-737CB21B56AC@.microsoft.com...
:I ran into same problem this what I did to fix:
: In the data I found something to group the data on. In my case it was
Month.
: Edit the new group and put a page break after or before the group. This
will
: Force a new page and when converted to excel it will put that month in its
: own tab.
: In you case You may be able to do location or department.
:
: Hope this helps.
:
: "Aileen" wrote:
:
: > We have a report that returns more than 65,000 rows that we need to
render to
: > Excel. Is there a way to make RS parse the data into multiple
worksheets, or
: > will we need to split the data into more than one report for rendering?
: >|||If you use the document map feature with your grouping you could break it up
to separate tabs very easily.
However, I think you're asking a bit much from a report generator. This is
not so much a report as a data dump.
jc82196 wrote:
>I ran into same problem this what I did to fix:
>In the data I found something to group the data on. In my case it was Month.
>Edit the new group and put a page break after or before the group. This will
>Force a new page and when converted to excel it will put that month in its
>own tab.
>In you case You may be able to do location or department.
>Hope this helps.
>> We have a report that returns more than 65,000 rows that we need to render to
>> Excel. Is there a way to make RS parse the data into multiple worksheets, or
>> will we need to split the data into more than one report for rendering?
Message posted via http://www.sqlmonster.com

Examples of Web ReportViewer with Remote Processing

We have tried a bunch of different ways to run reports in the ASP.NET Web
ReportViewer. Every attempt to do it ourselves has failed to render.
We have a number of examples of local processing in Web pages. Heck, we
even have built a number of Windows Forms applications that use both local
and remote processing. But we cannot find anything that will cause ASP.Net
to render.
Is it possible that using the Viewer in this case does not work?
Walt Crosby
Chief Architect
Everyday Wirelessdoes your RS and ReportViewer server are on 2 different servers?
and do you use the NTLM authentication?
if yes, you suffer Kerberos issue, search on the MS web site to know how to
setup it.
can you send the the code of your ASPX page which contains the control?
"Microsoft" <Walt.Crosby@.everydaywireless.com> wrote in message
news:ugKGzreWHHA.600@.TK2MSFTNGP05.phx.gbl...
> We have tried a bunch of different ways to run reports in the ASP.NET Web
> ReportViewer. Every attempt to do it ourselves has failed to render.
> We have a number of examples of local processing in Web pages. Heck, we
> even have built a number of Windows Forms applications that use both local
> and remote processing. But we cannot find anything that will cause
> ASP.Net to render.
> Is it possible that using the Viewer in this case does not work?
> Walt Crosby
> Chief Architect
> Everyday Wireless
>|||The Reports Manager and ReportServer are on the same machine as the Web
Site. We have used Report Viewer many times from Windows Forms applications
with very few problems. We have yet to find any examples of Remote Server
processing with Web Report Viewer...
Walt Crosby
"Jeje" <willgart@.hotmail.com> wrote in message
news:1215D799-3869-4CAC-8550-3C5B049AC185@.microsoft.com...
> does your RS and ReportViewer server are on 2 different servers?
> and do you use the NTLM authentication?
> if yes, you suffer Kerberos issue, search on the MS web site to know how
> to setup it.
> can you send the the code of your ASPX page which contains the control?
>
> "Microsoft" <Walt.Crosby@.everydaywireless.com> wrote in message
> news:ugKGzreWHHA.600@.TK2MSFTNGP05.phx.gbl...
>> We have tried a bunch of different ways to run reports in the ASP.NET Web
>> ReportViewer. Every attempt to do it ourselves has failed to render.
>> We have a number of examples of local processing in Web pages. Heck, we
>> even have built a number of Windows Forms applications that use both
>> local and remote processing. But we cannot find anything that will cause
>> ASP.Net to render.
>> Is it possible that using the Viewer in this case does not work?
>> Walt Crosby
>> Chief Architect
>> Everyday Wireless