>>>>for save:
>>>> - if the object that has the focus has a controlsource, set the focus to it [ = write value to disk buffer ]
>>>> - table update
>>>> - form refresh()
>>>>
>>>>for cancel
>>>> - table revert()
>>>> - form refresh()
>>>
>>>We have form refresh in Save and Cancel methods of the form. However, for some unknown reason it's not enough for array based comboboxes. Only explicitly calling combo's refresh fixes the problem.
>>
>>Nadya,
>>
>>It may have something to do with the fact that the combo's list of values does not accept the current value of the combo (and style = 2)
>>
>>If that is the case, add the unaccepted value to the array (for a test ) and see whether it still behaves badly
>
>Adding blank value doesn't fix the problem.
_________________________________________________________

>>>We have form refresh in Save and Cancel methods of the form. However, for some unknown reason it's not enough for array based comboboxes. Only explicitly calling combo's refresh fixes the problem.


Like Fabio asked, is the combo on an inactive page ?

Also, put some trace in the form ( a la Acti screen ?'tablerevert' and 'form refresh' )

look at the sequence of the events (acti screen output)

I would not expect (and I may be wrong) array based combos to behave differently

It must be in the sequence of events (set value - set focus - revert/update - refresh)
Check that sequence

Even make it a field based combo (cursor as source) and see what happens