>It is a normal use of the Interactivechange() event handler of a combobox control to perform calculations on other controls whose values may be affected by any change in the value of the combobox. But if your calculations are extensive, an unexpected effect may result. The combobox's display does not update.
>
>This defect appears to arise because the combobox is on a timer. If the display is not updated within the time set by the timer, the display will not update at all.
>
>This defect is similar to a timer-related problem in VFP3.0 in which the combobox would not drop its list when mouse-clicked if the activity resulting from instructions in the GotFocus() event handler exceeded a certain interval. That problem appears to have been fixed in VFP5.0.
>
>Anyway, if the display of a combobox does not update, the solution is to set .displayvalue = .value at the end of any InteractiveChange() processing. At least this is the only workaround I have come up with.
>
>Has anyone investigated how VFPs combobox is constructed? I am curious whether to expect any other timer-related problems. Also if you have a more elegant workaround than setting .displayvalue, I would love to hear about it.
>
>Thanks.

Your question is too generic. Basically, combo is fixed anytime by pushing Combo.Value=Combo.Value (if something strange appears:). Beyond this, it works Ok.