>>
>>As to why method has to belong to a form. I don't know (can't see) where else this method would belong. That is, I add/create a method in the form that enabled/disables certain buttons. At run time the code in each text box event OnTextChange needs to "know" if this (parent) form class has this method or not. So in the OnTextChanged method I need to determine (at run time) if the form class has this method.
>
>
>Dmitry,
>
>I'm not in a position to give expert advise - but let me give a thought
>
>I do not think the GetPemstatus is the .net way - it belongs to the IDE in development mode
>
>Are your forms based on a common (sub) class. If so, you can add a method to the subclass that does nothing. Each textbox can call the method
>If you need some code in it why not override that method in the forms that need it ?
>
>You can make that more explicit by defining an interface and have your common sub class implement that interface. All the forms can override the method
>
>Depending on what you want to do, you can even add an eventhandler to the form, or add a class/object to the form that is reponsible for that behaviour
>
>The textbox' OnTextChange event can forward that event to that class/object you have added to the common subclass form.

Gregory,

Thank you very much for your input. And I also thought about the approach you bring up: creating a base class of a form with a method that I need. All that you say makes sense. Many choices.