FWIW, you might want to, in the future, use the ideas of hooks. (I think I'm finally "getting" them < s >). Instead of putting code in the basic methods in objects derived from classes, put a post-action method in the parent class. Then the basic method in the parent can call the post-action method when it's done. Put the object specific code in the post-action method.

Of course, this might be pre-action code, instead < g >.

Otherwise. Like the others said, just get in the habit of doin' a dodefault when you code base methods.

Good luck.

>Hi. I have a question.
>
>Example: An application is in-place with a few thousand text boxes based on the class AtxTextBox. In some of these text boxes there is coding in the LostFocus method for whatever reason. Time passes. Now a request is made to change the behaviour of the AtxTextBox. Lets say it is a request to change the ForeColor property when it has focus. I would think coding a ForeColor change in the GotFocus and LostFocus methods would make sense. The problem is that any of the controls based on the AtxTextBox control that have coding in the LostFocus method will not run the default code (changing the color back). Is there a simple way around this or will these text boxes have to be found and a DoDefault() stuck in all of the problem children.

...snip