>Why would you say this is a weird design?
>My combo class is loaded from a lookup table. If I didnt see an item that applied to the record, I would see the "Edit ... Type" bar and it launches a dialog and it becomes blindingly obvious what to do next.

Just that normally, a combo is used only to select an item from a list, and not to perform an action (like a command button). I am a fairly experienced computer user, and this would confuse me...

>I agree the button is a decent idea, however with the button, I would
>have to have the tooltip text set, not a big deal either, but the combo
>is already open, whereas with the button, I have to try it once the
>first time just to see what it does. Also, with the button idea, I would
>now have to have a button class to go along with the list, whereas the
>list automagically sets itself up from a table.

Ok, I didn't realize that this was a class, and not a single situation. You're right: a single control is cleaner.


>I dunno; six one way - half dozen the other I guess.

Just another idea here...
I have a combo class and an accompanying form that takes a table name as a parameter that allows you to right click the combo to edit the table. The "Edit Lookup Table" form allows inserts, updates, and deletes, as well as changing the sort order. The right click is not intuitive, but users quickly learn how to do it, and after that, its a breeze to implement and to use.