Yep, I see what you are saying.

I think what I said before is correct, with an exception:

c.AddItem "Test2",2 will add "Test2" before item 2 if it exists-however, if it does not then it won't add it at all.

I agree with you that the combo boxes are lacking. One would expect them to behave like a standard combo box.

Perhaps the folks at Codejock with recognize this as a bug, or consider it for a future enhancement.

Would you consider using a custom control (standard ComboBox) instead? Then you should have the functionality of a standard combobox. It's not the best sollution but...

Drop a combo on your form (Combo1)

Dim mCustom     As ICommandBarControlCustom

Set mCustom = CommandBars.Add(xtpControlCustom, id, label)
With Combo1
   mCustom.Handle = .hWnd
   .AddItem "Item1"
    .AddItem "Item2"
    .ListIndex = 1
End With

OK, then why don't any of the items in my list appear?

Try adding items using index values like 3, 4, and 5 (in that order) and you'll see that no items appear in your combo box.

Also - there is no "ItemData"-type property for the combo boxes then so you can associate ID values with combo list items? That's practically the whole purpose for having combo boxes. Some functionality is severely lacking here.

jamauss,

I think this is normal. It appears that the 'index' parameter is like the 'before' parameter in a VB collection (although the object doesn't support named arguments).

 c.AddItem "Test1", 1
 c.AddItem "Test2", 2
 c.AddItem "Test3", 2

Is like saying:

add Test1 before anything

add Test2 before the 2nd item (if it exists)

add Test3 before the 2nd item (if it exists)

So the list would be: Test1,Test3, Test2

rob