Getting Started

Re: Problems in Exporting to Excel 2007

EJLindsay — Mon, 13 Oct 2008 08:34:40 GMT

What do you mean "use excel functionality". Give me an example.

Thanks.

Jay

Re: Problems in Exporting to Excel 2007

chinnivasudeva — Mon, 13 Oct 2008 07:29:52 GMT

Use Excel functionality (include excel.dll features) instead of using

Response.ContentType = "application/vnd.ms-excel"
Response.AppendHeader("Content-Disposition", "filename=Data.xlsx;")

Excel functionality will solve your problem.

To know about the MS Office 2007 warning message check the link: 
http://blogs.msdn.com/vsofficedeveloper/pages/Excel-2007-Extension-Warning.aspx

Re: Problems in Exporting to Excel 2007

chinnivasudeva — Mon, 13 Oct 2008 07:26:50 GMT

Use Excel functionality (include excel.dll features) instead of using

Response.ContentType = "application/vnd.ms-excel"
Response.AppendHeader("Content-Disposition", "filename=Data.xlsx;")

Excel functionality will solve your problem.

Re: Problems in Exporting to Excel 2007

savemickey1 — Thu, 15 May 2008 15:49:42 GMT

This does not solve the issue of Office 2007 renaming the file to download.aspx, which causes the error message when excel tries to open.

Here is the code. It worked fine before Office 2007 was installed.

if (Request.QueryString["file_id"] != null)

{

SqlDataReader dr = File_DAL.DownloadFile(sqlConn, Convert.ToInt16(Request.QueryString["file_id"]));while (dr.Read())

{

Response.ContentType = dr["MimeType"].ToString();

Response.AddHeader("Content-Disposition", "filename=" + dr["FileName"].ToString());Response.OutputStream.Write((byte[])dr["FileImage"], 0, (int)dr["FileSize"]);

Response.End();

}

dr.Close();

}

Re: Problems in Exporting to Excel 2007

karyani — Thu, 15 May 2008 13:55:56 GMT

See my post from 04-11-2008, 8:25 AM

Re: Problems in Exporting to Excel 2007

savemickey1 — Thu, 15 May 2008 02:08:10 GMT

I am having the same problem with downloading 2007 files. The word and ppt files open fine but they are named download.aspx. Excel doesn't like the aspx extension so gives me an error but still opens fine once I click ok. This issue has to revolve around the fact that 2007 doesn't open its files in IE windows, but in the programs themselves. If anyone has any updates on this please let me know.

Re: Problems in Exporting to Excel 2007

Nachos — Wed, 30 Apr 2008 17:38:52 GMT

Now, about that message.

The O2007 message could at least state how Joe User should go about determining a file is not corrupt before opening it, so users wouldn't call their developer every time they download. I wouldn't know how to verify my dynamically-generated file is not corrupt without trying to open it and then probably looking through, and I've been a developer eight years.

More details on my experience with this message :

"The file you are trying to open, 'blah blah.ext', is in a different format than specified by the file extension. Verify that the file is not corrupted and is from a trusted source before opening the file. Do you want to open the file now?"

Application A generates a file on-demand, .xls only, as a response stream to a browser, with .xls extension and type application/vnd.ms-excel. Its content will vary with the GridView. The client whose latest Office version is 2003 loads this .xls with no complaint; but for the same file, the Office 2007 box returns The Message, naming 'such-and-such.xls' as the file I'm trying to open. Seems like Office 2007 is insisting on itself converting the .xls to an .xlsx.

Application B uploads and downloads files using SQL Server as its store. Content is stored as a binary field, MIME file type descriptions are stored, filenames are stored with extensions. Before I changed "inline" to "attachment" per Karyani's post, results for .xls files (coming in as an .aspx-format response) were the same: The client whose latest Office version is 2003 loaded this .xls with no complaint; but for the same file, the Office 2007 box returned The Message, naming file 'downloadFile.aspx' as the file I was trying to open. Here again, Office 2007 converted the .xls to an .xlsx.

For Application B when downloading files as .xlsx or .docx, Office 2007 complains it found unreadable content, but of course that would be a different issue. Just thought I'd lump it in in case any one else is hitting the same part of this Office 2007-download-related continuum. Files besides Office 2007 download with no warning flags on both my dev boxes. What is UP with Office 2007 upload and download?

Application A and B have in common the same server for dev environment. For prod environment they also share the same server, and it's a different server than for their dev environments.

Re: Problems in Exporting to Excel 2007

Nachos — Wed, 16 Apr 2008 21:03:20 GMT

Kudos Karyani!

For .xls files, that's eliminating this particular message, on my application that involves a DataGrid and SQL Server. Incidentally, that application had been failing to download Word 2007 files; this edit fixed it.

On the other hand, for the application I tried this with earlier, I continue to get the message.

Differences between the two apps follow.

App where the message persists (App A):

2.0 .Net C# SqlServer2005 (file not stored in SQL though) GridView

Does not store the file content in a database rather sends it directly to the browser as a Response

App where the Excel 2007 message stopped appearing and also the Word 2007 download was enabled by this edit (App B):

1.1 .Net VB SqlServer 8.0 DataGrid

App first redirects to a blank aspx where the Response is composed.

App A (rendering GridView grvRequestors to a Response)

string attachment = "attachment; filename=Requestors.xls";

Response.ClearContent();

Response.AddHeader("content-disposition", attachment);

Response.ContentType = "application/vnd.ms-excel";

StringWriter sw = new StringWriter();HtmlTextWriter htw = new HtmlTextWriter(sw);

grvRequestors.RenderControl(htw);

Response.Write(sw.ToString());

Response.End();

App B (download a file whose content is stored as binary in SQL)

When users clicks to download:

Response.Redirect("./downloadFile.aspx")

in downloadFile.aspx

Response.AddHeader("Content-disposition", "attachment;filename=" & dsAttachments.Tables(0).Rows(0)("FileName"))

Response.ContentType = dsAttachments.Tables(0).Rows(0)("FileType")

Response.BinaryWrite(dsAttachments.Tables(0).Rows(0)("Attachment")) 'content

Response.Flush()

Re: Problems in Exporting to Excel 2007

karyani — Fri, 11 Apr 2008 12:25:19 GMT

I solved this problem by storing in the database the file extension (FileExtension ) when it is uploaded.( .xlsx or .xls)

Then when opening the file from the database I check the extension and use

Response.ContentType = "application/vnd.ms-excel"; Response.AppendHeader("Content-disposition", "attachment; filename=” + name + FileExtension);

Response.BinaryWrite(the binary file);

Re: Problems in Exporting to Excel 2007

jobejufranz — Mon, 31 Mar 2008 10:22:40 GMT

Hi Guys,

Please refer to http://forums.asp.net/p/1101709/2265897.aspx#2265897 as it may help you.

Re: Problems in Exporting to Excel 2007

Nachos — Thu, 27 Mar 2008 20:24:03 GMT

Same problem.

Re: Problems in Exporting to Excel 2007

swathi556 — Wed, 27 Feb 2008 05:04:46 GMT

I have same problem...any solution?

Re: Problems in Exporting to Excel 2007

ageuni — Thu, 07 Feb 2008 02:32:36 GMT

I am also having the same problem...any solutions floating around out there?

Re: Problems in Exporting to Excel 2007

dclash — Thu, 31 Jan 2008 19:47:19 GMT

Has anyone resolved this issue? I am having the same problem.

Re: Problems in Exporting to Excel 2007

TonySmith-Brewster — Mon, 19 Nov 2007 14:20:41 GMT

I am also having the same problem, it seems that we are not alone with this issue either. I have browsed the web for a few days but to no avail. I set up an xml filestream from an aspx page, it works fine in Excel 2003 but not in 2007. I do not believe that this problem will ever be resolved for Excel 2007. Regards TSB.