Error reading Excel sheet with #! type error - REXX

On Nov 7, 9:22 am, lontjr <lon...@triad.rr.com> wrote:

>     13 *-* Say '('iCol','iRow'):' myWorkSheet~Cells(iRow,iCol)~Value
> Error 92 running H:\My Documents\Source\ooRexx\tExcel.rex line 13:
> OLE error
> Error 92.902:  Cannot convert OLE VARIANT to REXX object: The
> conversion of the
> VARIANT type VT_ERROR into a REXX object failed.
>
> Using oorexx 3.2.0 on XP with SP2, Excel 2003 with SP3.
>
> The cell in question has a simple #VALUE! error, but I'm not able to
> query it ahead of time to avoid this error, nor can I trap the error
> with any Signal/Call condition ("any" fails to trap it).

Go to the project on SourceForge and open a bug for this.

https://sourceforge.net/tracker/?gro...01&atid=684730

If you attach a spreadsheet and a simple ooRexx program that produces
the problem to the bug, I can mostly likely get it fixed for the next
release.

If you attach the files, I'll see if I can come up with a work around
to use with ooRexx 3.2.0.

> There was a similar question here in 2004, but no reply.

If a bug had been opened at that time, which was before I joined the
project, along with a program to reproduce it, it most likely would
not exist in 3.2.0. <grin> I fixed every oleObject bug that was open
at the time I joined.

We are trying to encourage everyone who uses ooRexx to participate
more in the project. Opening bugs with a way to reproduce the bug is
extremely helpful participation.

> Discussions in ref guide on OLEObject and OLEVariant don't seem to
> speak to this kind of error.  

There are a number of VARIANT types that are not / can not be used in
OLE Automation. I'm not an expert in OLE Automation, (which is why I
need a program that produces the problem.) It may be that I, and the
original designers of oleObject, thought that VT_ERROR was in that
category. I'll have to look through the code.

> Can we have a clue harvest here?

Sure, provide a way to easily reproduce this and I'll see what I can
do.


--
Mark Miesfeld