>>>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.

Yupp. At the form level the load was added to give you a chance for needed actions like opening cursors / tables and so on. Add logging the own name in each init and watch. vfp init#constructor!

regards

thomas