>>>The method is called from the Init. Setting ListIndex to 0 doesn't work.
>>>
>>>Then it must be something in the framework because, as I said before, testing with a base class combo and a base class form, setting the listIndex to zero worked just fine.
>>>
>>>The problem with setting the combo's value to something that is not in the list may allow you to save invalid data if the combo is a bound control.
>>
>>Absolutely agree. A dangerous way to remove selection.
>>Listindex=0 has always worked for me. Alternatively she could set value to .null. or key in Ctrl+0.
>>Cetin
>
>I don't think it's framework related but rather data related. Try to create a list with cUserID and cEmpName. Put few items with empty cUserID and not empty cEmpName. Set the RowSourceType to 3 (select-statement). See, if you can reproduce this behavior.

Nope I can't. My combo and listboxes (if not all almost all of them) already have rowsourcetype 3-SQL and I always use Listindex=0 successfully.
Maybe you could provide a reproducing code?
Cetin