Yes, I also get the extra firings on startup. My interest is using assign to create events where maybe we are short some. Do you have any examples? I thought Kevin's setall was a good one in Fox Advisor article.

>>Thanks for looking at this. I'm trying to see what I'm missing about this. This is my simple test, and yes there was a sneeky refresh in my navigation button class:)
>
>Looks like I am guilty of the same test pollution: I started again with all base classes, and subclassed the textbox to contain only a Value_Assign method, and get the same results as you. Looks like I have some egg on my face... once I got the test laid out right though, I found some other interesting results- the Value_Assign method fired thrice when the form started, and I would've expected only once- you get this? Also, checkboxes, editboxes and textboxes fire their value_Assign methods on control.GotFocus.
>
>None of this however, changes my viewpoint on the value of Value_Assign methods though- now that we have confirmed that it fires on control.Refresh(), only confirms that we have a new place to put code that we could have previously placed in the refresh method without all of the unexpected event firing.
>
>Thanks for pushing me to test these assertions...