On Thu, 10 Feb 2011, Taro App wrote:
Oops, there's a comment that isContinueNext "Should never be called before end of current record" so the code must be correct.
Or at least correct to the best of our knowledge...
I'm not sure how it happens, but the exception is raised when POI tries to read phonetic text in ExtRst of UnicodeString. POI tries to read 18 double-byte characters, but RecordInputStream has only 29 bytes (14 characters + 1 byte.) If I check the Excel file with binary editor, everything up to here seems correct.
Hmm, the phonetic text stuff went in much later to the file format. It's not impossible that the team working on it had different ideas about continue records to the team who did the original work
When I open the excel file and deleted sheets which do not contain the problematic string, then the problem disappeared. I tried deleting different sheets, then the problem sometimes disappeared and sometimes not. I also tried re-inputting the problematic string by cut & pasting in Excel, then the problem always disappeared. My best guess is that Excel sometimes saves corrupted data. Corruption occurs in phonetic texts which is not usually visible to users, it is not very obvious.
If you open the file in Excel and do "Save As", does it fix the issue, or is it only changing text / removing sheets that fixes it?
Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
