Hi everyone, I get this exeption when I try to export a grid with row layouts
at Infragistics.Documents.Report.Grid.GridCell.set_RowSpan(Int32 value)
at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridDocumentExporter.CreateReportCell(List`1 reportRows, DocumentColumnInfo documentColumnInfo)
at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridDocumentExporter.ExportNormalCell(UltraGridRow gridRow, UltraGridColumn gridColumn, List`1 reportRows, DocumentColumnInfo documentColumnInfo)
at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridDocumentExporter.ExportNormalRow(UltraGridRow row, ITable table)
at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridDocumentExporter.ExportRow(UltraGridRow row, ITable table)
at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridDocumentExporter.ProcessGridRowInternal(UltraGridExporterHelper ultraGridExporterHelper, UltraGridRow row, ProcessRowParams processRowParams)
at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridExporterHelper.Infragistics.Win.UltraWinGrid.IUltraGridExporter.ProcessRow(UltraGridRow row, ProcessRowParams processRowParams)
at Infragistics.Win.UltraWinGrid.RowsCollection.InternalTraverseRowsHelper(IUltraGridExporter exporter)
at Infragistics.Win.UltraWinGrid.UltraGrid.Export(IUltraGridExporter exporter)
at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridDocumentExporter.Export(UltraGrid grid, ISection section)
any help would be appreciated in knowing what could be wrong.
Thanks, jose
If it's not fixed, you should Submit an incident to Infragistics Developer Support and include a small sample project demonstrating the problem.
I download the hotfix, installed and upgraded. But that did not solve my problem. It is still throwing the same exception. Help?
Yes, I beleive the first hot fix for v2008 was release last week. You can see the announcement here: BLOGS: Vincent McDonald
So there is a hotfix for 2008 VOL 1?? I recently upgraded from 2007 VOL 2 because I thought this would solve the exception problem but it didn't.
Jose
Hi Jose,
An issue like this was recently fixed. Get the latest Hot Fix and the problem is most likely corrected.