Export to Excel / Worksheet

The other day I was working on some code to export data to excel. I usually create an XML file, which can be read with Excel 2003. The problem though was that the size of the XML file can become very huge and sometimes it would take quite some time to do the exportation based on the amount of data. I would say that for small amount of data this solution still works, however for me it was just not useful anymore. I was looking for a third party control, which could export the data right away to Excel, without requiring any Excel on the server and which would be fast enough to generate a big excel file. I tried few components, but I think the best and most useful control is Aspose's Excel - with just few lines of code you are ready to export the data to an excel worksheet. I love the ImportFromDataReader function :) Ofcourse there are other goodies in the component included as well, like charting, summing, etc.. The component works in both ways read and write. I recommend it to everyone.

Published Friday, September 08, 2006 9:50 AM by Sonu
Filed under: , , , ,

Comments

# re: Export to Excel / Worksheet

Wednesday, November 22, 2006 4:48 AM by Swathi
Solution required : How to display export to excel in atlas in dotnet 2005

# re: Export to Excel / Worksheet

Wednesday, November 22, 2006 9:08 AM by Sonu

You might want to post this question in our atlas forum, so that other users can help you as well.

http://dotnetslackers.com/community/forums/4/ShowForum.aspx

# re: Export to Excel / Worksheet

Tuesday, January 16, 2007 2:33 AM by Sreejith Rajan
Hi All, Am using ASP.NET 1.1 & C# code in exporting data from SQL SERVER to Excel sheet. I came accross Funky charcters. Data in SQL SERVER DATABASE: Berglunds snabbköp DATA when Exported to Excel sheet: Berglunds snabbköp Any help from your side will be appreciated. Thanks in advance. Sreejith Rajan. Software Engineer, DUBAI

# re: Export to Excel / Worksheet

Friday, April 06, 2007 6:31 PM by Shawn
As for the funky charcters, it is most likley because the special characters in new fonts are generally unicode characters and not extended ascii. this means when moved between application applications it does not get translated propperly. The unicode is char is broken down into 2 standard characters hence the funky look. So you need to have a destination which supports unicode or you need to translate any character above 128 or 256 in the standard ascii character set into something else. You see this alot when emailing unicode characters in HTML email in this case you need to do a HTMLEncode for any character above 128. You so not want to do the whole text because you may need to keep the < > tag character.