>>No joke. We do use it for one thing. We have a TreeView and a ImageList in a container. Our baseclass TreeView has some code it's init to set the .ImageList property to the ImageList object, so the ImageList object has to instanciate first.
>
>In that case, I would add them both to a container and add code to the container's Init to do this. If they both have to exist for either one to exist, this makes sense to me. Otherwise, add code in the form's Init to handle this. I just hate to rely on a user-defined instantiation order. Relying on the instantiation order set internally to VFP is not a problem for me.
>
>Just my $0.02.

Actually, it's old code that's been around for along time. When we added the 2 controls to the container, we probably should have moved the code out of the TV.Init and put it in the container Init. But since it ain't broke...