Hi Shannon
No matter what Microsoft tell you about lookup fields, combo boxes belong on
forms, not in tables.
A combo box usually shows a list of options derived from another table.
Let's say you have a field in your table named ContactType, and you have a
table named ContactTypes with the following data:
CtpID CtpName
----- ---------
1 Employee
2 Customer
3 Associate
4 Supplier
5 Friend
The idea is that the ContactType field contains the number corresponding to
the option on the list, but the combo box displays the text.
The combo box has several properties that control what is displayed and
stored from the list. To set up this example, you would set these
properties as follows:
ControlSource: ContactType (the name of the field where the value is to
be stored)
RowSourceType: Table/Query
RowSource: ContactTypes (the name of the table, or even better:)
RowSource: Select CtpID, CtpName from ContactTypes order by CtpName;
ColumnCount: 2 (the number of columns in your table or query)
BoundColumn: 1 (the column which contains the value to be stored)
ColumnWidths: 0 (the width of the first column - this causes the first
column (the numbers) to be hidden so that what you see is the text)
--
Good Luck :-)
Graham Mandeno [Access MVP]
Auckland, New Zealand
"mugziegumz via AccessMonster.com" <u47747[ at ]uwe> wrote in message
news:8e6bfbe81b830[ at ]uwe...
[Quoted Text]
|