>The inter-dependent things may better be solved in a custom method of the form, which gets called from whenever necessary - form's activate, or control's refresh etc, depending on some condition (like - if your third combo's displayvalue is impty or something like that). This way you have several checkpoints which take care of your combos, and call the check'n'rebuild code, which checks if refresh is necessary.
>
>Though this may sound like an overkill, I've found that such distinct methods serve me well, because soon I discover they should be called from some button's .click, some other textbox's refresh, from the rightclick menu and from a toolbar button. This gives me a little abstraction - the action is in the method, and triggering the action is attached to interface elements.

You are right on target, Dragan. That's the way I operate, too, using an independent custom method to do this sort of job...as you say, you may soon find it re-usable during runtime, and all the code is in one place, which is a big plus, also, outweighing object independence in this situation...