Hi Robert,

BindingSource is the name of the business object name that is registered with the form and accessess the lookup table. If there is no business object, you could use the standard Combo Box properties rather than the MM properties to bind it to data.

With MM the idea is to sycnrnoize the lookup table to the table it used for. So if you have a table where these lookups are used as a child you would set the BindingSource to the lookups BindingSource, typically set the BindingSourceDisplay member to field you want to have display in the combo such as the Name field, then set the BindingSourceValueMember to the value such as the PK that would be matched to the parent table.

This would get the values bound to the Combo box and display the name, but to get the synchroniziation to occur to the parent, you need to set
the combo BindingValueSource to the Business object of the parent and the BindingValueSourceMember to the foreign key in the parent where the lookup's PK is used to match them up. This would cause it to synchronize.

Based on your response it sounds like you do not have an actual table and business object for the lookups, but you are creating a table in code? You said you didnt' see why you needed a table, but you described one so just need clarity on that. Also are you sycnhronizint this with a parent table?
Tim


>Hi Tim. I have a combobox to display 8 items. I do not see any reason as to why I need to create a table for 8 records.
>Here's what I'm trying to do:
>
>I have a table called "Lookups" with 3 fields (PK, Name, Type)
>
>PK is the table primary key
>Name is the name of the lookup. i.e. BLD can be Building 9
>Type can be:
>AGC - Agency
>BLD - Building
>COR - Class of Restriction
>COS - Class of Service
>RTY - Request Types
>STY - Status Types
>UNT - Units
>VEN - Vendors
>
>BindingSource is Lookup (table mentioned above)
>BindingSourceDisplayMember is Type
>BindingSourceValueMember is Type
>
>Thanks.