UPDATE: While Googling for "incremental combobox", I came across a message that talked about the VFP "Builder", which sounded like it is a PEM wizard of sorts. So in the form designer, I added a new, 2nd, combobox and right-clicked on my combobox object and chose Builder... Well that gave me an error "File c:\program files\microsoft visual studio\vfp98\wizards\listbldr\listbldr.vcx does not exist". That led me to a MSoft KB article Q191499, which basically states that MSoft forgot to install these critical files! Yikes, just what a newbie needs, right :) Onward we go... Turns out you have to unzip a file called XSource.zip, which contains all the source for the VFP "builders", as well as the class libraries (.VCX). I put the listbldr\*.* files in the path specified by the error message, as I did not know how VFP would find them otherwise...

Now the Builder works without errors - cool. Back to my 2nd combobox that I added. My goal was to see if a combobox created by the "Builder" would incrementally search. Turns out it does! Then I start comparing my 1st combobox's properties against the one the Builder made. Only differences were ColumnWidths and RowSourceType. The Builder assigned 2 column widths, probably because I manually sized the columns in the builder's Style tab. As for RowSourceType - the Builder used "6-Fields" whereas I used "2-Alias". So then I changed my newbie-built combobox's RowSourceType to "6-Fields". Hey, now it does incremental searching too! Finding it hard to believe that there is any difference between 2-Alias and 6-Fields, I changed my combobox back to 2-Alias. Run it. Guess what, it still works!!! I put it back to the way it had been all day, and yet it now does incr searches. My only conclusion: when the Builder did its magic and found missing listbldr file(s), maybe that is what really made my original combobox work? But it only took several hours today to get a combobox to work as advertised - this is going to be fun - NOT :)