I wasn't able to reproduce this issue using an UltraComboEditor with a few items added to it, the DropDownStyle set to DropDownList, and the DropDownWidth set to -1 (which didn't seem to do anything). Are there any other conditions that you have to reproduce this issue? The first thing that I would recommend is that you have the latest hotfix to see if that fixes anything.
-Matt
The issue centers around having a row in the datasource with null member values. This results in a blank row shown in the combobox, but the comparison logic fails since it's a null item being compared to a keystroke letter (string) value...
Set AutotComplete property to "True" to be able to reproduce the issue
Even when I set the newer AutoCompleteMode property, or the obsolete AutoComplete property, I didn't get an exception when there was a row having null values for both the DisplayMember and ValueMember. You should submit a small sample to Developer Support, or also ensure you have the latest hotfix, as mentioned previously.
I can reproduce it everytime with the exact settings from above. It is very annoying.
-Ken
Ken,
Likely this has been addressed in the latest hotfix as mentioned then. I can't really do anything from here, but Developer Support should be able to verify if it has already been fixed, or what version it was fixed in.
Did you ever resolve this issue? I'm facing the same problem. I am using version 2008.1 but I can upgrade to 2008.3.