>After spending hours trying to get a combobox dopdown to work as most people/users would expect, I find all sorts of threads on this topic that seem to conclude that the native combobox's dropdown is imperfect - at best. I'm talking about its odd behavior when incremental searching is enabled: once the list drops down, it immediately closes upon any keystroke ***if*** the mouse pointer should happen to be within the rectangular area of the dropdown list. It behaves this way regardless of whether combo is in a grid or not...
>
>I find it odd that VFP comboboxes in the developer interface work "properly", yet the native combobox class that MSoft gave us for runtime do not work the same. SO MUCH FOR OOP AND REUSABILITY, I GUESS MSOFT'S DEVELOPERS MISSED SOME OOP CLASSES :)
>
>In case any MSoft VFP developers are reading this, try dropping down the PEM's own combobox at top of Properties window to see a list of all objects. That list does not collapse when I type, regardless of where the mouse pointer happens to be. Could you make the native combobox work this way too?

Frankly the combo box is not the greatest control. It's often abused. How do I put 400,000 customers in a combobox is a far too frequently asked question.

I use Visual MaxFrame and it includes a textbox that replaces the combobox.

There are combobox classes that can be found in the download section of the UT. Maybe one of them will work for you?