Oh, so you manually populate your combos? What do you do when you have 100 or so items in a lookup? Do you use AddListItem?

Please continue....

You must have some very code intensive applications...

>Value will be empty, but not necessarily DisplayValue combo.style=0). So, follow your suggestion, a user can pick-up empty item, and your code will think that this is new displayvalue, and attempt to insert new empty record to lookup table.
>I write it specisically for you, not for a sake of logics.
>
>>I think you are looking at this in a backwards fashion...
>>
>>The FK will not correspond to a value in the rowsource, and as such, the displayvalue will be empty
>>
>>Often however, folks do place empty values in the database. Nothing wrong with that approach.
>>
>>I know what you are saying here. The logic you are throwing out here however, does not jive...
>>
>>
>>>What, if you have empty item within a list? Should I proceed with 'Gee..' line now?
>>>
>>>>Ed...
>>>>
>>>>Often, if not most of the time, the displayvalue NEVER equals the value. The best solution is the one he found himself: If Empty(This.Value)... Gee, and he isn't an MVP.
>>>>
>>>>>>IF NOT (This.Value==This.DisplayValue)
>>>>*** insert record into table etc.
>>>>>>ENDIF