>ALthough it looks like the perfect place for it, there are several issues with Value_Assign that make it a bad candidate for this, IMHO.

OhOh...

> Having any code at all in the Value_Assign method of a class causes the GETFLDSTATE setting for the bound field to change when the refresh runs.

Strange..., this is a bug or "by design"?

>also, there are a couple of situations where Value_Assign doesn't when you would expect, so I don't think it will do the job satisfactorily.

Can you point me to some of them?

> You are, of course, welcome to try.

It's all our life, try, error and try again. :)

>My base textbox class has a custom method called anychange that is called from both the InteractiveChange and ProgrammaticChange events at the class level. This way if I need code to run no matter how the value changes, I can put it in the AnyChange method. You can also choose to call it from the Refresh method to cover all your bases.

Good! Thanks for the tip.