Update: the code runs when clicking on a combobox item but does not if the number is typed in and the pointer exits the box. But the problem still exist if the code is in the lostfocus event. The combobox does not have a value if the user types in a value. So the method is never called.
Chuck
>Ok smarty pants, what should I have called it? The method use to be in the combobox valid and did the same thing. I created the method thinking the pointer movement would change its behavior and it didn't. Its like the code never runs. I suspended the process in debug, AFTER the method ran and manually did a parent refresh in the command window and no data appeared which means to me the code did not execute because no values are in memory. Problem is sometimes it works and I donot know how to trap it.
>
>>Chuck
>>
>>So why did you head your thread "erratic combobox behavior"? What's happening/ not happening exactlty to the combo?
>>
>>
>>>Terry
>>>Its not the combo that needs refreshing, its the grid. Yes I do have a gridRefresh method that runs in the valid after the grid columns are supposed to be updated. Its like the code never runs, but in debuf step mode it works, so weird.
>>>
>>>>Chuck
>>>>
>>>>Not sure whether you're saying here that the combobox is not refreshed - there's no mention of it in your sample code. Off the top of my head:
>>>> are you .Refresh()ing the combo after you add values to its source?
>>>> are you .Requery()ing it?
>>>>
>>>>HTH
>>>>
>>>>Terry
Extreme Programming = Plan -> Design -> Code -> Test