Hi,

  I am getting a weird behavior on Apache POI but is having a hard time on
how to find a fix.  The scenario is, I have a .xlsm file that I converts
(using my laptop - 32 bit windows environment) into .xls file then process
the .xls file using Apache POI, on this event, it works perfectly fine.  But
when I converted the .xlsm file into .xls using a different system (64-bit
windows environment) and process the .xls file using Apache POI, I am now
getting an exception, saying:

  Exception in thread "main"
org.apache.poi.hssf.record.RecordFormatException: Unhandled Continue Record
followining class org.apache.poi.hssf.record.HeaderFooterRecord
        at
org.apache.poi.hssf.record.RecordFactoryInputStream.readNextRecord(RecordFactoryInputStream.java:357)
        at
org.apache.poi.hssf.record.RecordFactoryInputStream.nextRecord(RecordFactoryInputStream.java:251)
        at
org.apache.poi.hssf.record.RecordFactory.createRecords(RecordFactory.java:442)
        at 
org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:287)
        at 
org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:250)
        at 
org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:194)
        at 
org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:329)
        at 
org.apache.poi.hssf.usermodel.HSSFWorkbook.<init>(HSSFWorkbook.java:310)
        at
org.apache.poi.ss.usermodel.WorkbookFactory.create(WorkbookFactory.java:64)


  And when I am opening the excel, I am getting this error: 
http://imageshack.us/photo/my-images/545/68616755.png/

  Does anyone encountered and be able to fix this issue?


Thanks.

--
View this message in context: 
http://apache-poi.1045710.n5.nabble.com/Unhandled-Continue-Record-followining-class-org-apache-poi-hssf-record-HeaderFooterRecord-tp5550087p5550087.html
Sent from the POI - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to