>Nick,
>
>>>One: I'm using Fields in FreeTables for all my ComboBoxes but for no particular reason. Are there reasons for using different types for different situations?
>>>
>>Difficult to say - it is up to you. :) It depends of what rowsources you have and what do you want to use.
>>Usually you use Fields when you have multicolumn listbox.
>>You may use Value for short list of items which never change, etc.
>
>All my ComboBoxes are single column: Country, State, Race, Religion, Court, Agency, etc. Is there a disadvantage to using FreeTable fields for all of these?

No, I don't see any disadvantages here. The variety of source types just means that you have the ability to use different sources, and which one is better in your particular case depends of what you want to accomplish.

For example: if you have another control in the same form which scrolls the same table (say Grid) , both controls will try to move the record pointer in the same table. In this case you may consider to use SQL Statement as a source type for one of them, in order to avoid this. But this is not about advantage or disadvantage of types - it just depends on how you planned this to work.

>
>>>Two: How do I get the Incremental Search to work? This property is set to the default (True) but has no effect on my ComboBox.
>>
>>Set Style property to 2 - Dropdown list.
>
>
>That worked great, thanks. If I want users to be able to add new items directly to some of these ComboBoxes will I have to set Style to 0 - DropDown Combo?

Yes, but you will loose the ability for IncrementalSearch :) You can try to swap the Style prperty at the runtime, but this is tricky - how your Combo control knows what you want - enter new value or do Incremental Search? You may use additional checkbox to select one of the functions, but the user may be confused anyway... :)

HTH,
Nick