>>>>UPDATE: I cleared the RowSource of the control (combobox) which uses the cursor. And the problem goes away. So it does seem like the problem is caused by this control. But the question still stands as to why the INIT of this control is never called?
>>>
>>>because the init is one of the last things happening... think about the events at the form level, where each and every aggregated control is added and then fires its init before the form init...
>>>
>>>HTH
>>>
>>>thomas
>>
>>I am trying to understand what you saying (and thank you, of course, for your help). Are you saying the control is first added to the container and then INIT of this control fires? If so, this is news to me.
>
>the order is this:
>- the control member is partially added to the parent,
> at this point
> parent.controlcount becomes + 1
> you can use the control member
> if you try to RemoveObject(control.name) VFP fire an error and can crash
>- the control properties are loaded
>- the control.init run
>
>VFP then must be able to assess the control properties before control.Init execution
Thank you for the explanation.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
