>>I'm sorry. What I actually meant to say is that I have a problem with the fact that the controlsource of a control (field it is linked to) is specific to each form. You can have exactly the same control on two forms that just have a different controlsource because they're linked to a different table. If you don't want to use a pre-defined dataenvironment you don't have another option then to set the controlsource in the init event of the form.
>>
>>Thanks for the quick reply,
>>Jeroen
>
>Jeroen,
>If you're opening tables programmatically, you should use the LOAD event, which runs before any of the controls instead of the form INIT which runs after the controls are intialized. This way all the tables will be open when the controls need to access them.
>
>Barbara

This thread grew up tremendously, and I wasn't on-line to make necessary comments. Sorry, Barbara, that I use you message as entry point; it's not directed to you :).
The right place to put some interface related code depends on the way developer designs the interface, i.e. what is nucleus of the application. If form itself is nucleus (incidentally, it's my way) then Form.Init event for startup operations (and Form.Destroy event for cleanup operations) is natural place, because here it's 100% guarantee that everything from design mode got initialized and available for manipulations. Surely, it doesn't mean that everything coded inside this event. Actually, this event calls some form/class methods and reset some form/class properties. IMO. that's so understandable, that shouldn't be repeated every time in every UT reply.