I have a UltraGrid, populated with cca 22.000 rows and and 10 columns at most (It never breaks 65536 barrier). When I export the contents of the grid to excel file, everything goes well, but when I want to open file with excel, it gives me following notification:Excel found unreadable content in 'export.xls'. Do you want to recover the contents of this workbook? If you trust the source of this workbook, click Yes.
When I click Yes, it tries to repair the damage but is unable to do it. The only column whose value gets exported is the one that is of type boolean.
I am using NetAdvantage for .NET 2007 Vol. 3 CLR 2.0 with latest (1043) patch applied. What could possibly cause this error? Column types are mainly strings and integers with the exception of one Guid and abovementioned boolean. I use no intermediate features of grid (ie calculated columns, summaries, etc.). It is simply a ultragrid bound to datasource. In all other cases throughout my application everything works fine with the exception of this grid which contains quite a lot of rows.
Best regards.
This might help as a temporary fix, but the Excel assembly should not be exporting corrupt Excel files.
We're having an issue with corrupt Excel workbooks as well. The code is fairly simple, it:- Opens the Excel file- Reads, line-by-line, the first column's cell, matches it to a string in an MSSQL database, and fills the second column's cell in with the matched string- Saves the Excel file
I can open the file and tell it to recover the file, and all the data is there, including the newly inserted data. Any cell formatting from the original sheet, however, seems to be gone. AFAIK if I don't specifically make any changes, the cell's formatting should be left intact, correct?
Any help, or should I go through another channel for more assistance?
That is correct. Cell data and formatting should be preserved in a round-trip operation assuming they were not manually changed. If you experience anything different, I would recommend submitting a sample demonstrating the issue to the support group: http://ko.infragistics.com/gethelp.
Are there any news regarding the corrupted files yet? We want to use this function in one of our products and we need a decision which component we use.
Louis
There have been a few bug fixes recently for bugs which caused corrupt files, although I'm not sure if the bugs specifically mentioned in this thread have been fixed. I would recommend trying to export a workbook with a small set of data that utilizes all the features of the Excel assembly you were planning on using in your final product. That way you can determine if our exporter is right for your product.
Hi everyone,
I've submitted the issue to the support group: http://ko.infragistics.com/gethelp. They've provided me with hotfix which fixed an export bug. I suggest you contact them in case you encounter any problems with export capabilities.