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...
I'm still not able to reproduce this issue. I tried binding the UltraComboEditor to a datatable where the DisplayMember column has a null value in one of the rows. When I tried typing a letter, there was no unhandled exception. Dropping down the list, the row with the null DisplayMember cell had its ValueMember shown instead.
Make sure that you have downloaded the latest hotfix. If this doesn't help, I would contact Developer Support with a small sample so that they can see if this has already been fixed.
Both the display and value members have to be null for the error to occur. The stack trace shows it then will try to do a string comparison, and that's where it fails...
I still can't reproduce this issue even in this scenario. You should definitely make sure you have the latest hotfix.
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.
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.
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.
I can reproduce it everytime with the exact settings from above. It is very annoying.
-Ken