>Hi Bob,
>
>you could achieve the same behaviour my putting this code intot he InteractiveChange, ProgrammaticChange and Refresh event. Unlike Assign methods, here you are not forced to change the value of the Value property.
>
>Christof
>

I thought using the value_assign event/method would be cleaner because I could keep all the relevant code in one method. (Although I also needed this.value = this.value in the LostFocus event because value_assign doesn't fire when the control is changed)

It seems we had a lot of the functionality for value_assign available in other methods and events. I've just been playing with these things and it's been interesting!

I think most of the behaviour makes sense when you think about what is happening and why, but sometimes our first view isn't quite as deep as it needs to be.