>...
>>
>>>>
>>>>I also have observed that when combo is in a grid, the first time I click on the combo's dropdown arrow, the list drops down for a brief instant, then closes. I have to click on it a 2nd time, and then the dropdown remains open. Until I type anything, at which point it closes. So I have 2 quirks occurring so far with combos inside a grid...
>>>
>>>Did you put the code I mentioned, above, in its .GotFocus()? Not sure but I guess the first click is "swallowed" by the grid. Don't know why the combo jitters though. You'd need to set a breakpoint in the grid's .GotFocus() and trace what's hap[pening.
>>
>>
>>No, I did not try adding that code yet. I do notice that ***every other*** time I click on the combo's arrow, the dropdown list flashes for only a second, then disappears. If I click on it again, it remains open. So I do not think it has anything to do with the grid stealing focus away from combo (as the grid is already selected).
>
>And why not? It's not a major system re-write to try it! By this process you'll come to realise why people end up using their own classes of the combo and not the bog-standard as you are seeking :-)

Actually, I did insert a WAIT 'Combo1 GotFocus' WINDOW TIME 2 in the combo's GotFocus event - so I could see every time it got the focus. I believe the "flickering" problem is happening because the combo's initial value is blank - and not contained in the list. It's interesting to compare the behavior of an identical copy of the combo placed outside the grid. It behaves quite differently.

What is a "bog-standard"?

I think I'd end up not using any of VFP's controls or classes if I "abandoned ship" every time I ran into an unexpected/unusual behavior :) Maybe VFP would be a better product if more people submitted enhancement requests to MSoft (assuming I actually end up finding a bug/quirk). Of course, creating your own combo-like object is always an option in a language as powerful as VFP. My perseverance does usually pay off for me in the long run. But I can understand that many others will not be as patient...

>
>>
>>I think I am going to start a brand new project and test grid-based combos more thoroughly. Maybe that fact that this project was created by the VFP 6 "converter" (from a FP-DOS 2.6 project) is making my life very difficult :)
>
>What? you on a research grant or something!? :-)


As a long-time programmer, I like to rule out potential causes. The VFP "converter" is a big unknown to me, so thought it might be smarter to rule it out...

And yes, having to learn a product as substantial as VFP is like being involved in a massive research project :)
>>
>>
>>
>>
>>>>
>>>>In my case the grid's column is a PartNumber field from a Products table. The combo is set up as 2 columns, PartNumber and PartDescription. I want the user to be able to type in the part number (if they know it), OR drop down a list of PartNumber/Description choices to pick from. I want the dropdown to incrementally search as they type. Am I asking for to much from this native combo control?
>>>
>>>And is it NOT actually incrementally searching as you type, even though the list closes? Does it get there when you put a valid part no. in?
>>
>>When I type the first character, it does incrementally search and move to the first matching item in the dropdown - but then immediately closes. I want it to stay open until I press ENTER or click on a choice.