Interesting. I'll have to think about that. I found my problem (see my reply to Barbara).

Thanks for the help.


>Hi Roi,
>
>I agree with Barbara, at the REQUERY action.
>But, as i've already had some problems with combos, i've created a combo class with:
>
>Properties:
>- Array_Name (keeps the name of the array)
>- Field_Name (the name of the field from the view, that will keep the information the user selects; it's like a CONTROLSOURCE)
>
>Methods:
>- LOADING ("fills" up the combo, with the information from the array)
>- CHOOSING (this method choose the correct line, because it compares the values of the combo with the value from the array, and apply for the right LISTINDEX).
>- At InteractiveChange event, i take the value from the array and save at the field (that is at the Field_Name property).
>
>
>Well, this sound stupid, but is a safe philosophy i have created months ago, because (this way) my combos are never "directly" connected to "something", and the information i give to user can be manipulated also (add a blank line, add a last line with the description "NEW RECORD", etc).
>
>Hope it helps,
>
>Ricardo