Well, the parent is the only common link you have, so I suppose you are doing it
right ?

Though I would try to minimise the actual parent's role in things.

I would uuummmmm, from within a child control, to FindControl() the parent (or
NamingContainer), and then FindControl() the child you want of that parent (or
use control  collection), thus not adding any additional code to the parent.

Thats just the way I'd do it, don't know what's sthe "right" way to do things.

I camw across something once where a control was in a page and the control was
being used by the parent in way I am not used to. I tend to, and try to, write
controls that are as independant as possible - but this one sort of minimised
the controls  independance and the container using it was doing half of what it's
work should have been.
I don't know ... it was MS and was bubbling events and all sorts ... but I just
had a natural oversion to the way it was set  up.
I'd like to know more myself to tell the truth.