You can move focus to another control programmatically from Combo.Lostfocus event (honestly, I don't know why it sticks to the combo), i.e. issue Thisform.AnotherControl.Setfocus (you may also add NODEFAULT if it won't move).
I used to have unbound combos and they save me from many quirks.
>Many thanks, Ed. The this.requery in the valid event looks pretty good. The added value is highlighted but the cursor stayed in the combo. I also tried it in the lostfocus. Here, the cursor stayed in a "blank" combo. Pressing Tab brought up the highlighted entry.
>
>Is this how it's supposed to work?
>
>Again, Thanks. You've probably saved me many hours of digging "on my own" to figure this out.
>
>>>I have many comboboxes that use fields from lookup tables as row sources.
>>>
>>>If the user types an entry that is not in the rowsource table, the entry is added to that table and the control source.
>>>
>>>Everything works fine except for the display of the displayvalue after all this occurs. If I move the cursor back to the combobox and tab out of it the display is as it should be.
>>>
>>>I test for the need to append in the valid event of the combobox.
>>>
>>>Does anyone have an idea as to how/when to show the proper value in the combobox soon after the combobox loses focus?
>>>
>>>Dale
>>
>>You can explicitly set Combo.Value(DisplayValue) property after you added new record in Combo.LostFocus event. It's safe to call Combo.Requery after you added new record to Combo.Rowsource
Edward Pikman
Independent Consultant