[V4Rb] VDatabase reference problem

[Charles Yeomans]

On Tuesday, June 17, 2003, at 03:42 AM, Ruslan Zasukhin wrote:

> on 6/17/03 2:38, Charles Yeomans at yeomans at desuetude.com wrote:
>
>> I finally tracked down the source of an intermittent error in my
>> application.  Unfortunately, it took me quite a while because
>> VBaseObject.Database.ErrNumber was not being set; looking in another
>> VDatabase object that pointed to the same database revealed the
>> problem. I can understand why this function returns a different 
>> object,
>> but it would be nice if the object properties were kept in sync so 
>> that
>
> Hmm, actually objects must be the same, otherwise we cannot avoid 
> problems
> like you describe.
>
> I need check this.
> I was sure objects are the same.

As it turns out, they are.  Let me offer more detail.

The problem was that V4Rb was returning error 666; my registration code 
obfuscation was returning a bad result.  What I am seeing is this:  the 
global database reference I hold and the reference obtained from 
VBaseObject.Database point to the same object.  But when I test the 
ErrNumber property, my global database reference returns 666, while the 
reference obtained from VBaseObject.Database returns 0.  This doesn't 
seem possible, but I am looking at it in the debugger right now.

Charles Yeomans