First off, thanks for the new "Contains" feature. It works great with one possible exception.

One of my WinCombo's datasource is a list of Statuses, two of which have DisplayValues of "Issued" and "Re-Issued". The AutoCompleteMode is set to "Suggest" and AutoSuggestFilterMode is set to "Contains" for this WinCombo. The auto suggest in combination w/ contains works great when an end user is making their selection but I have hit an issue with this. I programatically set the value of this WinCombo when another form event fires and even though I am setting the valuemember for "Issued" , the WinCombo auto suggests both "Issued" and "Re-Issued."

Upon further investigation, the value portion is set properly but even though it has a valid value, it suggests more options (based off of the new "Contains" property). What bothers me is that this happens even if the control doesn't have focus. I know how to determine if a WinCombo is dropped down and also close it but I certainly don't want to have to put this type of extra processing throughout my application.

So my question is this, is this a "Bug/Issue" or is there a property that I can also enable/disable on the WinCombo to correctly take advantage of the "Contains" AutoSuggestFilterMode?

-Ian