Hi Sergey
This was doing my head in so much I just opted for the Access/Assign methods in the BizObj property of the container which will assign/request using the Form object directly, rather than holding an additional reference, all works ok now.
Thanks
Kev
>Hi Kevin,
>
>Maybe this.Source get changed somehow?
>
>>Hi
>>
>>Still having problems with this, so I'll go into a bit more detail.
>>
>>The form contains the main first instance of the BizObj which is a reference to a BizObj in a Collection on the form, so let's say BizObj is referencing thisForm.BizObjects.List.Item(1)!
>>
>>BizObj contains another BizObj called Person, which in turn contains another object called Address.
>>
>>One of the containers on the form has a property called BizObj and in the refresh will do:
>>
>>this.BizObj = EVALUATE(this.Source)
>>
>>
>>In my current situation in which the error occurs, I'm creating a whole new instance in thisForm.BizObj, refreshing the form, and then the container picks up on thisForm.BizObj.Person fine, no problems.
>>
>>After a 2nd refresh it seems to fail, when it issues the above line of code, the thisForm.BizObj instance seems to lose the Person Object, and it's as if the container "snatches" the instance, rather than referencing it.
>>
>>I've monitored this in the Debugger and it happens before my eyes, I'm looking at Container.BizObj and thisForm.BizObj.Person and the latter simply dissappears (thisForm.BizObj is still there, just not Person).
>>
>>Sorry about the level of detail, but this is driving me up the wall. The front-end app is VFP6.0 and the BizObjects are pulled from a VFP8.0 COM DLL.
>>
>>Thanks, hope this makes sense.
>>Kev
>>