Exporting to Excel seems like a feature that everyone wants to see. I feel as though if I'm not mimicking or automating Excel in some way, I'm dumping data directly into it. Anyways, you can Google dozens of ways to get an ASP.NET 2.0 web application to export to Excel.
Weather you are generating an XLS on the fly and merely redirecting to it, creating Excel-friendly HTML on your page, or even (and Microsoft says this is a major no-no) coding against the Excel object model on the server, your users will inevitably want to see rows and columns when the browser stops spinning.
And like I said, there are several well-documented ways to do this. These can be divided into two different methods:
In order to force that Open button to actually bring up Excel, just insert a little bit of love into the page's markup. Here's what I did:
Normailly, you'll see this code in a souce file instead of the markup ala Classic ASP (which, barf, I'm not a fan of). However, by placing it here, we are focing the page itself to ooze into Excel; the page is poised to always be in "Excel client world." When the same code is behind an event handler, it will cause the Response object to pipe the HTML into an Excel browser since we are still in "web world."
And there you have it! I've never seen happier users...