I use the following code:

Private Sub RbtnExport_SelectedIndexChanged(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles RbtnExport.SelectedIndexChanged
Dim sFile As String = Session("User") & "-Customer List-" & Today()
sFile = sFile.Replace("/", "")
RbtnExport.Visible = False
Select Case RbtnExport.SelectedItem.Value
Case "Excel"
Response.ContentType = "application/x-msexcel"
Case "Word"
Response.ContentType = "application/msword"
End Select
Response.AddHeader("Content-Disposition", "Attachment; filename=" & sFile)
End Sub

To allow a user to save a web page with a datagrid on it into an Excel
sheet.

They'll run a page using a Web check box, which renders it to an ASPX page,
and then when they have the final product on the screen, they click the
radio button for Excel, and it prompts them to Open or to Save the file.

The problem occurs when you save or open the file.

The datagrid has 9 columns in it, a product code, description, unit of
measure, price, product hierarchy number, weight and UPC code, etc.

The data grid has a header & a footer on it, and each column in the datagrid
is sortable.

If I have a short list, one of maybe less than 20 records, I can click the
Excel button, it prompts me to save it, and it'll save as a document with a
..xls extension. You can then open it up without incident.

If the list is longer - say maybe over 40-50 rows in length (up to the
longest list, with up to 500 or more items in it), it will save it with a
..xls extension, but you cannot open it.

Excel attempts to open it, but it immediately gives you an OK box that says
"Unable to read file". It works fine if the number of rows is small (under
25 or so), but not if it's much more than that. Thus far, I have not seen a
pattern in it. The file that will open is 20K in size, the one that will
not is 400K in size. I have figured that the difference is between 30 and 50
records before it gives me this problem. I've noticed that each line
appears to add about 1K in file size to it the excel file.

It doesn't appear to be a memory issue, as excel works fine any other time,
and will open spreadsheets much larger than this. I've confirmed that it's
not version specific in Excel, as it barfs on every version of excel it
tries to open it in.

Any idea as to what is going on here on this problem? Is there any way I
can step thru the open of the file in Excel, to see the specific problem
Excel has with opening the file?

Any help/advice appreciated.

Thanks,

SC