Hi!

Well, VFP controls give you only very basic functionality. Many things you require to customize. The behaviour you mentioned is not so obvious. What VFP should do: add item to combobox list, or add it to the RowSource - the view used to populate that list? Well, if you think it is obvious and can describe it well, post this to the VFP 8 wishes list document, so maybe it will be updated in the next version of VFP. If you want more advanced functionality already ready, buy good framework that usually have such combobox with code in classes to organize all this and even more. Well, if you do all by self, than program combobox by self.

PS: This is a difference between programming and constructing applications. Programming is what you require to do to make combobox do what you want. Construting is just dropping combobox, specifying properties and go further. This thread is pretty good sample to see difference ;)

>I guess what's not really clear is why this is all necessary. If the concept behind a Combobox is to select from a list or enter a value, why does it not handle that automatically? If I type a value in a Textbox I do not need to do a replace; the fact that I have it tied to a ControlSource is enough. I do understand why the AddItem would be used, but when do you need the AddListItem? It's a lot of coding to get the Combo to do what you would think would be native behaviour.
>
>Renoir
>
>>Yes, replace is required too:
>>
>>lcVal=this.DisplayValue
>>REPLACE (this.ControlSource) with this.DisplayValue
>>this.AddItem(this.DisplayValue)
>>this.Refresh
>>
>>AddItem and AddListItem methods of combobox add items to the list in combobox that is displayed when you hit the combobox drop down arrow. What is not clear here?