Our application has the need to open workbooks that have been saved in the StrictOpenXml format. Calling the workbook's load method generates "Input string was not in a correct format." with the following stack dump. Any help would be appreciated.
No, I don't think so. Excel can open either format, but only saves in the format your controls can read. The one that your control is able to read has 50 4B 03 04 14 00 06 00 as the first eight bytes. The one that Excel is able to open but your control is not has 50 4B 03 04 14 00 08 00 as the first eight bytes. When the file is changed in Excel and saved, the first eight bytes change to 50 4B 03 04 14 00 06 00.
My impression is that the generator of the file is not using Excel, but something else to produce the file. The 06 verses 08 in the seventh byte refers to the type of compression within the file; the format with 06 in the header indicates that the compression method is "imploded" and the format with 08 in the header uses the compression method "deflated."
Hm, that's interesting. So that means that it's not the format itself that is causing the problem, but some particular data in the Excel file.
I have not sent a file because the act of removing sensitive customer information results in the problem going away since it is then saved by Excel. I am in the process of getting permission to provide a old version of the information that would be less sensitive.
dana
Hi,
I am just following up on this. Did you send in a file we can use to test with? If so, I don't think we received it. Can you send it again?
I will check into it, but my guess is that the Infragistics Excel engine will not support using some other compression method. Although if that is in deed the problem it's odd that it would work in some cases and not others.
It would still be helpful if you could send me a file to test with.