>The application I'm working on uses the logic of having the first entry (default) in the RowSource as a space so that the user can select this if they choose an incorrect entry. For example, if the user inadvertently picked an option, without the blank available they would only be able to choose another option. This doesn't seem like a good interface to me. Is there a way for the user to easily revert the CombeBos to an empty value without having the blank in the list? Thanks!
>
>Regards, Renoir

Dragan Nedeljkovich suggested another approach, using blank field command instead.

Basically, that's a problem with comboboxes. This is the letter I sent my colleagues about the same problem (didn't receive an answer on it):
---------------------------------------------------------------------------
Hi everybody,

I raised the ComboBox problem once several months ago. Looks like this problem still exists in our applications, because we didn't come up to the absolutely workable solution, which could be applied for all cases.

First of all, let's determine, that cases could be:

1) RowSource Table doesn't have a blank record, but the field (ControlSource) accepts Blank Code

2) RowSource Table does have a blank record and the field (ControlSource) accepts Blank Code

3) RowSource Table does have a blank record and the field (ControlSource) does not accept BlankCode (example, Data Entry screen Town field).

Now, I believe we already added Blank primary code into each of the Lookups table.

How should we deal with the situation, when the underlaying table doesn't have a Blank Code?

There could be two possible solution here:
1) Use a Union clause in the select statement to include BlankCode
2) Have a method of a combobox, which will blank the field (it could be called by RightClick and pressing delete button).

I like the second solution more, because it's easy to implement (it will require Class change in wgcombobox, though).

What do you think about this problem?