VarOr / oleaut32

Hiya,

What app shows this? Can I get hold of it - I should be able to knock something up for it as a test regardless, but it might not be til mid next week.

Jason

[Ben Clewett]

[e-mail] wrote:
> Hiya,
>
> What app shows this? Can I get hold of it - I should be able to knock something up for it as a test regardless, but it might not be til mid next week.
>
> Jason

It's a VB6 application of our own description.  I have not had a chance 
to hack the source code to see where it comes into play, but probably 
something to do with a third party DLL we use for remote database 
connectivity.

Thanks for the offer of a fix.

I was hoping there was a generic fault, and somebody might have a 
generic fix.  Since it seems to be more indepth, I will try any get an 
exact location of location of failure first.

Ben

[Andreas Mohr]

On Mon, Dec 16, 2002 at 09:20:18AM +0000, Ben Clewett wrote:
> [e-mail] wrote:
> > Hiya,
> >
> > What app shows this? Can I get hold of it - I should be able to knock 
> > something up for it as a test regardless, but it might not be til mid next 
> > week.
> >
> > Jason
>
> It's a VB6 application of our own description.  I have not had a chance 
> to hack the source code to see where it comes into play, but probably 
> something to do with a third party DLL we use for remote database 
> connectivity.
>
> Thanks for the offer of a fix.
>
> I was hoping there was a generic fault, and somebody might have a 
> generic fix.  Since it seems to be more indepth, I will try any get an 
> exact location of location of failure first.

Even though I now implemented VarOr, I guess you might want to be careful
about that and use a native oleaut32 instead, since oleaut32 contains
tons of variant calculation functions (mul, add, and, xor, various
conversions, div, round), so if there's *any* bug in there affecting
some function your program uses, boom goes your data eventually.
That's why I'd use native oleaut32 for production use.
OTOH I'm still waiting for some builtin oleaut32 test reports ;)

> It's a VB6 application of our own description.  I have not had a chance 
> to hack the source code to see where it comes into play, but probably 
> something to do with a third party DLL we use for remote database 
> connectivity.

There's a significant number of Var* routines not implemented. I implemented 
the missing ones for a VB6 app I had written, but each app executes different
ones, so there's still quite a few missing. If you try the patch already
submitted, see if you get further and potentially hit other missing functions.
Most of the missing fn's are not too bad to implement, so keep reporting them

Jason