I have a hierarchical grid with 6 levels. When I export the grid to Excel I get no errors reported but:

a) the process of exporting is very slow (30s to export a simple grid with fewer then 30 rows of data, and thats on a v. fast system: quad-core @3.4Ghz, 8Gb RAM, 320GB SSD, 64-bit Win7 Ultimate). Totally unacceptable performance given that real-world data could have hundreds of rows.

b) not all of the data is exported - the final (deepest) level of the hierarchy is missing in Excel although it is displayed in the grid. I understand that Excel has a nesting limit of 8 for data outlining so we are well within that. Again this is unacceptable.

I ensure that just prior to export the grid is fully expanded and showing all of the data. My code to perform the export is: (where WEX is the ID of the WebExcelExporter).

WEX.ExportMode = Infragistics.Web.UI.GridControls.

ExportMode.Download;
WEX.DownloadName = "CapitalCostAnalysis";
WEX.Export(WHDG1);  // WHDG1 is the Hierarchical Data Grid

Am I doing something wrong or is this another example of major flaws? I'm beginning to lose faith in this software; it seems buggy, inefficient (hierarchical grids are hopelessly slow to load) and poorly documented (many of the examples show trivial stuff but are of limited help for real-world situations where much more detail is required. Many methods and properties have no details giving a description of their intended use or function). Some of the code examples just don't work at all (in IE8).

Anyway, whinge over. Any ideas for the Excel export problem?

Pual Shearing

IG 10.3
CLR 4.0
VS 2010