>David-
>
>Shoot. I'm sorry. I started to reply, then got distracted. :) Anyway, you're correct that my example does not apply.
>
>>Even though my explicit requery after the append fails to rebuild the list, subsquently clicking on the combolist apparently does cause it to be rebuilt automatically, because the new value (a blank) does appear and the combo listcount has increased by 1.
>
>Since you say the new item IS there when you click on the combo, why do
>say "Even though my explicit requery after the append fails to rebuild the list?"

Because the value of LISTCOUNT does not change after my explicit requery. However, after clicking on the combo to open the list, the LISTCOUNT bumps up by one.

Couple of other clues.

The purpose in life for the form I'm working on is to add work orders. Hence the commandbutton ADDWO. At the very end of the init for the form, I explicitly call the click of the ADDWO button to get the user started on the first work order. Wasn't sure if this was kosher (initiating a click from the parent container prior to the latter's exiting its init event method).

Another big clue. I backed off and set up a simple test form with just the combo and the button (each one set up exactly the same as in my real one, theoretically), and it worked. Clearly, I have some code my real form that's upsetting the applecart.