I do not typically use bound controls because they rarely function as desired. I prefer to populate them myself so I can do things like adding "Select a value" as the default, etc. And the value most certainly does exist - I can find it by looping through all the VALUES in the combobox using the code described in the original post, which is clearly pointing to the combobox value property.
However, as anubisascends insists this code will work (not sure exactly which code he was refering to), I tried them all again. I can still find no "cbo.value" property whatsoever. So I assume that's not the code he's referring to. Nor does "combobox.SelectedIndex = combobox.FindString("40")" work any better than it did last time, despite the fact that there is such a VALUE associated with an ITEM in the combobox.
I have noticed that if the DISPLAY column happens to begin with the very same text as the VALUE Column it will find the value (findstring does a substring search of the DISPLAY Column only), but not if there's a difference, which may be why his (?) code works where mine does not:
DISPLAY Value
Employee E
Executive X
Supervisor S
cbo.findstring("S") returns 2, but cbo.findstring("X") returns 0, incorrectly selecting Employee rather than Executive. According to Microsoft at:
http://msdn2.microsoft.com/en-us/library/wxyt1t12.aspx
I should be getting a -1 since none of the DISPLAY coumn values begin with "X", so returning a "0" when neither the DISPLAY or VALUE column for index 0 starts with an "X" appears to be a VS/FW error to me.
In any case, perhaps anubisascends' DISPLAY columns start with the same character(s) as his VALUE columns and that's why it works for him, because in my observation it works only for the condition described above, and is not only non-functional when the VALUE bears no resemblance to the DISPLAY value, but appears to be returning an erroneous result. Or perhaps the difference is that I am trying to select a value in a populated combobox, not retrieve data from a table as he appears to be doing? In any case, these solutions do not work in my instance.
I have yet to find something that will work other than the code shown earlier, but frankly have moved on to other projects at this late date anyway. Sorry to those hoping to find a solution here, but
AFAIK, there is none and the solutions suggested in this thread do not appear to work.