As an add-on to an existing database front-end application, we have allowed the user to export their report's data to Excel. Following POIFS' standards, we used C++ to write the Excel file. Upon testing, we discovered our code works perfectly for files under 6.8 MB. For files larger than 6.8 MB, it is necessary to use an XBAT. Excel will no longer open the file. The error message states the file is not repairable and cannot extract data from the file.
We adapted the code to calculate the number of XBATs needed and made appropriate changes to the self-description in the BATs. I've even gone so far as to compare our generated file in HEX to an Excel XP file. Everything looks the same for same-size files with the exception that we do not compress our string table. At this point, OpenOffice will successfully open the file but Excel will not. If we save the OpenOffice file as an Excel file, it does open properly. Since we cannot ask our customers to do this, this is not an viable solution. What potential pitfalls might we have fallen into? I'm thinking the problem is related to our implementation of the XBAT, but I'm not sure since it looks the same as an Excel XP file. I'd be more than willing to provide a generated file to anyone who is able to help. Thanks in advance. Brandon Belvin Information Systems Support, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
