Yes.
Typically this new table has a foreign key to the existing one, and a
foreign key to another one. For example, to store people's choices in music
you would need:
- a Music table (one record for each type of music);
- a People table (one record for each person);
- a PeopleMusic table (one record for each combination of person + music).
The form you use for People has a subform bound to PeopleMusic.
The subform has a combo box (choices from Music table).
For the person in the main form, add as many rows as you need to cover all
their tastes in music.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Reply to group, rather than allenbrowne at mvps dot org.
John Lute said:
Allen - thanks for the info! This brings up another issue for me:
"Do not use this to store values in a table. Multiple values belong in a
*related* table, and a subform is the appropriate interface."
So I need to make another table that has all the values I want - relate
it to my main table and then make a subform for this?