Bug 46094 - Unhandled Continue Record
Summary: Unhandled Continue Record
Status: RESOLVED DUPLICATE of bug 46137
Alias: None
Product: POI
Classification: Unclassified
Component: HSSF (show other bugs)
Version: 3.0-FINAL
Hardware: Sun Solaris
: P2 normal (vote)
Target Milestone: ---
Assignee: POI Developers List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-26 23:40 UTC by Joerg Bruennert
Modified: 2009-02-13 13:01 UTC (History)
0 users


Attachments
the corrupt Excel File (456.00 KB, application/octet-stream)
2008-10-26 23:41 UTC, Joerg Bruennert 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Bruennert 2008-10-26 23:40:38 UTC 
Hello,

when i parse the Excel File from Attachment i get the following error.
Exception in thread "main" org.apache.poi.hssf.record.RecordFormatException: Unhandled Continue Record
        at org.apache.poi.hssf.record.RecordFactory.createRecords(RecordFactory.java:168)
        at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:246)
        at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:169)
        at org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:298)

We use POI 3.0.2-FINAL, the same Error occured when i use 3.1

The File was originally created with Excel 2000 but since i made changes with Excel 2007 in this file i get the "Unhandled Continue Record"

Any suggestions what i made wrong?
Comment 1 Joerg Bruennert 2008-10-26 23:41:46 UTC 
Created attachment 22779 [details]
the corrupt Excel File

the corrupt Excel File
Comment 2 Nick Burch 2008-10-27 09:39:11 UTC 
Please re-try with poi 3.2, and re-open the bug if your problem still remains
Comment 3 Joerg Bruennert 2008-10-28 04:58:02 UTC 
The same problem with poi 3.2-FINAL
Comment 4 Josh Micich 2009-02-13 13:01:16 UTC 
(In reply to comment #3)
> The same problem with poi 3.2-FINAL
> 
But the problem does not occur on svn trunk now.  The fix was with a more recent  bug 46137 that is probably a duplicate of this.


*** This bug has been marked as a duplicate of bug 46137 ***