Re: Excel/POI - Here We Go Again -- RPG400-L

Yes, Scott, it was me who had the problem with the open. And you did tell
me how to fix it. I'm using the 'access' API and it works beautifully. The
problem is that the workbook DOES exist.

Yes, I know it exists. If it didn't exist, you couldn't possibly get theerror you posted.

I'm missing something. Why are you telling me about the access() API? Imean, I'm glad it helped you, and I'm glad that part of it is working, butit's not really relevant to today's error message.

You wrote a message this morning saying (I'm paraphrasing) that youthought it was strange that HSSF_open() would return 0 (which is *NULL)when it got an error opening a file. I told you that I changedHSSF_open() so that it traps any error reported by the Java routines, andif an error occurred that preventred it from opening the file, it returns*NULL. Yes, I did this in response to the SAME issue that caused you touse access(), but that doesn't make them the same thing!

So it's not strange that you're getting a zero returned. That's what it'ssupposed to do when it receives an error. Not just a "file not found"error, but ANY error. (RPG is not capable of monitoring for a particularerror message to be thrown from Java, it has to trap all possible errors.)

Now, in production, the original sheet has been emailed to the salesman,
who's changed it and emailed it back to me. I save his sheet to my desktop
and then drag it to the 'inbound' folder in the IFS. I don't know what
version of Excel he uses to save his sheet. Should it matter? I've tried
re-saving his sheet using MY Excel version and the read ('open') still
fails.

It could very well matter. Obviously Excel 2003 supports more featuresthan Excel 2002. And I'm sure Excel 2002 supports more features thanHSSF.