>>No, my advise is to remove thisform.Refresh() from InterActiveChange and put it in LostFocus(), or refresh only these controls, you needed, but not whole form.
>
>There can be circumstances that require a refresh of one or more controls - or even the whole form - on every change of value, so done from the interactivechange event. This is a functional design decision. The programmer should not say 'no' to such a design merely because of the limitation we have discussed here.

But you should take into consideration the laguage limitations. You can put all in some endless loop, but you didn't do this.
This is similar, bind control to Form property, then Refresh the same control BEFORE that property changes and you want all to works as you want. Maybe this will helps (but not tested):

*** InterActiveChange
LOCAL lnVal
lnVal = this.Value
thisform.Refresh()
this.Value = m.lnVal