Hi Michael.

>> I guess the confusion comes from the idea that i've never tried a combo bound to one field with another rowsource. <<

Typically, this is precisely the reason to use a combo. The RowSource of the combo provides the values from a lookup table. The combo is then bound to a value in a data file. Usually it is bound to some foreign key field. That foreign key is the primary key of the value in the lookup table.

>> If I were to refresh the view, and the field value was not in the list, would the combo.displayvalue correctly show the field value? (I will test this) <<

If you want to bind the combo to a value that is not in its RowSource, you need a custom class to do this.

SET PLUG ON

Get a copy of 1001 Thigs You Always Wanted To Know About Visual FoxPro (but were afraid to ask) when it is published by Hentzenwerke next month. There are two examples of such classes in the book.

SET PLUG OFF

Otherwise, you have to take action to add the newly entered item to the combo's RowSource.

Marcia