Re: xlread in 3.6.0

[PhilipNienhuis]

Please don't top post. Just reply BELOW relevant stanzas, to make it easier
to follow the discussion. You might also switch html off - makes it even
more easy to read. Thanks.

Read on....


I just installed 3.6.1 from Octave-Forge and got the same error as 3.6.0. My
answer is in the quote part. Thanks for helping.

PhilipNienhuis wrote
> 
> Actually this question belongs to the octave-forge mailing list (xlsread
> comes from the octave-forge io package) => cc'd
> 
> 
> 
> Some counter questions:
> 
> - What operating system?
> *Windows XP sp3*
> - Are you talking about the very same .xlsm files that were read from OK
> in 3.4.3 but no more in 3.6.0?
> *Yes, exact same xlsm files and exact octave code*
> - Could you please run (in Octave-3.6.0 then):
>       chk_spreadsheet_support ('', 3)
> ('' = empty string) to get more diagnostics about what does work and what
> doesn't?
> 3.6.1
> Checking Excel/ActiveX/COM... not working.
> 
> Checking Java support...
>   1. Checking Java JRE presence.... OK, found one.
>   2. Checking Octave Java support... Java package seems to work OK.
>   Java (version 1.6.0_29) seems OK.
>   Maximum JVM memory:   248 MiB; should better be at least 400 MB!
>     Hint: adapt setting -Xmx in file "java.opts" (supposed to be here:)
>    
> C:\Octave\Octave3.6.1_gcc4.6.2\share\octave\packages\java-<version>\java.opts
> Java support OK
> 
> Checking javaclasspath for .jar class libraries needed for spreadsheet
> I/O...:
> 
> Basic POI (.xls) <poi-3> <poi-ooxml>:
>   - C:\Octave\Octave3.6.1_gcc4.6.2\lib\java\poi-3.jar OK
>   - C:\Octave\Octave3.6.1_gcc4.6.2\lib\java\poi-ooxml-3.jar OK
>   => Apache (POI) OK
> 
> POI OOXML (.xlsx) <xbean> <poi-ooxml-schemas> <dom4j>:
>   - C:\Octave\Octave3.6.1_gcc4.6.2\lib\java\xbean.jar OK
>   - C:\Octave\Octave3.6.1_gcc4.6.2\lib\java\poi-ooxml-schemas.jar OK
>   - C:\Octave\Octave3.6.1_gcc4.6.2\lib\java\dom4j-1.6.1.jar OK
>   => POI OOXML OK
> 
<snip>


> 3.4.3
> 
<snip>


> Basic POI (.xls) <poi-3> <poi-ooxml>:
>   - C:\Octave\Octave3.4.3_gcc4.5.2\bin\poi-3.7-20101029.jar OK
>   - C:\Octave\Octave3.4.3_gcc4.5.2\bin\poi-ooxml-3.7-20101029.jar OK
>   => Apache (POI) OK
> 
> POI OOXML (.xlsx) <xbean> <poi-ooxml-schemas> <dom4j>:
>   - C:\Octave\Octave3.4.3_gcc4.5.2\bin\xbean.jar OK
>   - C:\Octave\Octave3.4.3_gcc4.5.2\bin\poi-ooxml-schemas-3.7-20101029.jar
> OK
>   - C:\Octave\Octave3.4.3_gcc4.5.2\bin\dom4j-1.6.1.jar OK
>   => POI OOXML OK
> 
<snip>


> 
>> It looks some Jar files were changed.
>> 
> 

At least the names differ. But before drawing conclusions, you could:
- Compare files sizes and md5sums of the Java class libs in the 3.4.3 and
3.6.0/3.6.1 Octave installations;
- Where they differ, try to copy the jar files from the 3.4.3 installation
over to the 3.6.x installation(s) and see what happens then.

Other than that, I have no clue what is going wrong.


On my box, 3.4.3 and 3.6.1 have similar javaclasspath entries as on yours
(i.e., their names differ in the same way between 3.4.3 and 3.6.x) but
otherwise they are the same size.

FYI, xlsopen.m (the function that creates the spreadsheet file pointer
struct) merely checks if the relevant jars are in the javaclasspath for each
interface. 
Proper operation of the Java class libs is only checked during the first
actual Java statements/method calls. If these fail (as seem to happen in
your case) I suspect something is wrong with them.

But again, I've never attempted to read .xlsm files.

If one of those isn't too big you could attempt to send me one, then I can
try to debug it IF it also fails here. I suppose you could easily decode my
email address.

Philip


--
View this message in context: 
http://octave.1599824.n4.nabble.com/xlread-in-3-6-0-tp4451557p4454951.html
Sent from the Octave - General mailing list archive at Nabble.com.