>Federico,
>
>This behavior is rooted in the way the controls update their controlsources. The update occurs when the control is losing focus. The interactivechange fires before the control has updated its controlsource, so teh Refresh call causes the control to reread its controlsource (which is still the previous value) and refresh its display to reflect the controlsource's value.
>
>This is a good example of why it si better to refresh specfic controls rather than the shot gun effect of refreshing the enitre form. If your InteractiveChange was to only refresh the other control you would not see this behavior.
>
>The THIS.Value = THIS.Value causes the spinner to update its controlSource with the new value and therefore the subsequent refresh reads the new value from the controlsource.

I gotta' tell ya', Jim, it seems to me in the short time I've been haunting this place that we can normally count on you to come through with the *reason why*. The above shows that what was thought to be a bug is actually normal behavior of the design, and a solid understanding of the design...in this case the firing sequence of events...helps us to avoid the lost time it takes to hunt his stuff down...like my hour yesterday with a check box doing something similar.

God, I LOVE THIS PLACE!!!!!!!!!