>>Leaving the combo unbound doesn't resolve the problem. There are two other combos also bound to the same object. The difference between these 2 working combos and the one non-working is the first two have 1 column and bound to it, the last one has 2 columns - the description should show. The second column is bound.
>>
>>Also, all the comboboxes set to be disabled - you can not change values in run-time.
>
>Okay, sounds like my idea wasn't it. Is the value numeric? If so, have you set BoundTo = .T.?
>
>Tamar

No, the value is character. I think I found some bad code responsible for the behavior. I adjusted the code and testing various scenarios now.