Bring to front and send to back at design time will do that.

But depending on instantiation order is dangerous, because you have litle control over it.
I think it's bad design, for VFP anyway.

>>When I run a form how do I determine which object's init runs first. Is it determined by the taborder?
>>
>------------------------------------------- REPLY ----------------------------
>Matthew:
>
>Sorry, I did not monitor the UT yesterday so my reply is a little late. But here it is....
>
>Every other OOP language I know of provides for a means of reordering objects so that you can initialize them in the order you need. VFP for some reason does not. This is a great pain in the very low part of the neck when you need control A to initialize so that control B can be initialized in a certain way depending on a property of control A.

>initiation time since all manipulation is done in the control's init() object -- not in the controls init() object then again at the container level. Since most of the controls on a form are irrelevant to firing order (labels and such), copy them in a block.

Just don't do it in the native Init() method then!
I have my own custom SETUP() methods for setting up controls.
ANd a custom Update() method of forms and containers.
Also a custom cleanup() method where I release object pointers.

It works better that way because I have more control.