I'm about at my wits end with the RadGrid support for excel exporting. Between it's horrible performance with largish datasets and it's inability to export my grid as it's seen, I'm looking for some other options here.
Has anyone in the Telerik community bolted on another excel export solution?
My thoughts here are just to take the HTML output from the grid, and parse it into something excel can read outside of Telerik's control.
See this link:
http://www.codeproject.com/Articles/164582/8-Solutions-to-Export-Data-to-Excel-for-ASP-NET
I really like the idea of being able to export a grid as it is seen on the screen. This provides a supurb user experience in the fact that they can configure things how they want, and then hit export. But this just isn't a reality with Telerik's built in support. Looking at my other threads with various problems I've been running into you can see the pattern of the problem. As long as you use the grid as is, or take your data directly from databinding it works great. Trying to use webserver side calculations, custom aggregates or export data with more than 20k rows and you're going to run into problems.
Any thoughts that may lead me to a workable solution would be great.
Has anyone in the Telerik community bolted on another excel export solution?
My thoughts here are just to take the HTML output from the grid, and parse it into something excel can read outside of Telerik's control.
See this link:
http://www.codeproject.com/Articles/164582/8-Solutions-to-Export-Data-to-Excel-for-ASP-NET
I really like the idea of being able to export a grid as it is seen on the screen. This provides a supurb user experience in the fact that they can configure things how they want, and then hit export. But this just isn't a reality with Telerik's built in support. Looking at my other threads with various problems I've been running into you can see the pattern of the problem. As long as you use the grid as is, or take your data directly from databinding it works great. Trying to use webserver side calculations, custom aggregates or export data with more than 20k rows and you're going to run into problems.
Any thoughts that may lead me to a workable solution would be great.