Re: Help using XLPARSER4

Scott,
Thanks for the clarifaction.  When I opened it in EXCEL and then went to Save As, the file type was Microsoft Exel 95.  After I save it as a current version workbook, I had no problem reading it.
 
Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2 
IBM  Certified Specialist- e(logo) server i5Series Technical Solutions Designer V5R3
IBM  Certified Specialist- e(logo)server i5Series Technical Solutions Implementer V5R3
  
 





----- Original Message ----
From: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
Sent: Thursday, October 16, 2008 5:00:37 PM
Subject: Re: Help using XLPARSER4

Hi Jeff,

Jeff Young wrote:

When I modified it for my application, I received the following error:
"java.io.FileNotFoundException: no such entry: "Workbook""

This error means that it *did* find your IFS file, but it can't find a
workbook object inside of it.

You see, Microsoft Office documents are actually archives in themselves
-- much like a ZIP file or SAVF.  They are archives of one or more
internal files.  So within your XLS file will be other, internal, files
that contain the spreadsheet, charts, images, etc... all the stuff that
can be placed in a spreadsheet.

So when it says 'no such entry: Workbook" that means that it's looking
for the Excel workbook inside the XLS archive.  And it's not finding it,
which isn't good.

Either the file it's reading isn't a valid Excel file (for example, a
Word document, or a PowerPoint document uses the exact same archive
format, but wouldn't have a 'Workbook' object because it's not an Excel
spreadsheet) -- or the file has been damaged somehow.  Perhaps it was
cut off during file transfer?  Or perhaps your file transfer software
attempted an ASCII -> EBCDIC conversion, which would've corrupted the
file?  Or perhaps it's an Excel format, but created from a version of
Excel that HSSF doesn't understand?

Hard to say.  I've never encountered this error in my own work...
everything I say above comes from searching the web for the error
message you posted...