Fred,

I got the culprit! It is a dangling reference alright.

Thanks
Dennis


>>Fred,
>>
>>I already did make the BO.oDataLayer = NULL in the Form's Destroy... still same.
>>
>>To review what I did:
>>
>>1. I pointed the Form.DEClass property to my DE Class
>>2. Then, dropped my BO on the form.
>>3. The BO has a oDataLayer property which I assigned as "=thisform.mydeclassname"
>>4. The form only calls methods of the BO, which is then relayed to the oDataLayer object reference, which is the DE.
>>5. The DE then performs its job, relays back to the BO, which relays back to the Form.
>>
>>Could it be because of a 'cyclic' reference? Is my way of referencing not allowed?
>>
>>Thanks again.
>>
>>Dennis
>>
>>
>>
>>>>Fred,
>>>>
>>>>Could it be because of the order of dropping the controls/objects on the form?
>>>>
>>>>Dennis
>>>>
>>>>>
>>>>>All I can tell you is it works for me. I recently had to do this for code for a ToolBar that was shared by many forms.
>>>
>>>No, it shouldn't be. If you clear it out in the form destroy, it should take care of itself. You already said if you don't populate that property, then the form (and datasession) close normally.
>
>
>
>If that's not clearing it up, then you may have some additional "hanging" object references elsewhere.