You should avoid binding events as an object (or it's delegate object) is in the process of instantiation.

Why is that? What kind of problems might this cause? While it seems to me the natural place to put it when having a class defined programmatically, I'd like to learn how to avoid it if I need to.

Thanks,


>James,
>
>You should avoid binding events as an object (or it's delegate object) is in the process of instantiation.
>
>I have also found out that VFP9 breaks a key function of BINDEVENT. It will always return the return value of the event source and never that of the delegate no matter how the flags are set.
>
>>I'm trying to bind some events in a textbox in a column of a grid to methods in the grid. The code looks like this (done in the INIT of the textbox)
>>
>>

      lcEvent='Click'
>>      BINDEVENT(THIS,lcEvent,THIS.PARENT.PARENT,'TextBox'+lcEvent)
>>      lcEvent='RightClick'
>>      BINDEVENT(THIS,lcEvent,THIS.PARENT.PARENT,'TextBox'+lcEvent)
>>      lcEvent='GotFocus'
>>      BINDEVENT(THIS,lcEvent,THIS.PARENT.PARENT,'TextBox'+lcEvent)
>>      lcEvent='When'
>>      BINDEVENT(THIS,lcEvent,THIS.PARENT.PARENT,'TextBox'+lcEvent)
>>      lcEvent='Valid'
>>      BINDEVENT(THIS,lcEvent,THIS.PARENT.PARENT,'TextBox'+lcEvent)
>>      lcEvent='LostFocus'
>>      BINDEVENT(THIS,lcEvent,THIS.PARENT.PARENT,'TextBox'+lcEvent)
>>      lcEvent='InteractiveChange'
>>      BINDEVENT(THIS,lcEvent,THIS.PARENT.PARENT,'TextBox'+lcEvent)
>>      lcEvent='KeyPress'
>>      BINDEVENT(THIS,lcEvent,THIS.PARENT.PARENT,'TextBox'+lcEvent)
>>

>>
>>This works for six of the eight events. That is, I can verify that the method in the grid is invoked as expected, except for Valid and When.
>>
>>Any ideas why this would be true?
>>
>>Thanks,