Right

No need to get shirty. I've been working exclusively in MapInfo and MapBasic for 2 weeks so terminology is a bit shaky. When you referred to rows I thought you were talking about combobox rows.

Now then, have you tried the interactivechange event of the combo? If I understand you, and your addendum to this message, you're not always adding to the combo, so valid wouldn't fire?

>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