hmm.. I didn't see the date, I was busy working...lol..
anyway, I have a workaround as I posted. I can reproduce this bug at will, simply by changing from combo to drop down list. When you do so, you lose your binding..sounds a lot like the bug in the website I referred to.
>Jeez Louise, John ... that is a very old post and bug (April 2003) ... it refers to the old 1.0 Framework and is not an issue anymore ... the ComboBox is fine in 1.1 and beyond. I use only DropDownList ComboBoxes all the time without a problem. It's probably something funky with MM's Combo.
>
>~~Bonnie
>
>
>>Found some more info on the drop-down list thingy....Apparently its a Microsoft bug in the combo box.
>>
>>
http://www.jelovic.com/dotnetbugs/>>Bug #15.
>>
>>
>>
>>>Hi
>>>
>>>This is the second post regarding an issue like this i have read, and i appear to be experiencing a similar (note similar) problem.
>>>
>>>The problem that i am experiencing with a combo set to DropDownStyle = DropDownList, is when attempting to execute code based on the SelectedIndexChange event. I am trying to update another field on the current row when the selection in my combo box changes. The update to the field (not displayed on form) occurs fine but my combo box refuses to maintain the selected value and just shows as blank.
>>>
>>>The combo still maintains the list items but no selection. Moving focus away from the combo and returning focus to it, and repeating the process, the combo now persist the user selection. WTF???
>>>
>>>Is there some underlying wierd thing happening here to our combos??? Can anyone shed some light on what is going on with our combos?
>>>
>>>Thanks in advance.
>>>
>>>Darren