One-to-many relationships are perfect for using a mainform and subform. Build
your mainform to operate off the ONE side. Add a subform and use the MANY
table as the recordsource. The primary key in the mainform is the foreign key
in the subform table and then they will link properly. Allow the subform
wizard to do that for you. If you have any questions about primary and
foreign keys, microsoft help has good explainations.
--
Milton Purdy
ACCESS
State of Arkansas


"Wizbard" wrote:

Sorry, the join is One to Many, Committees to Households.
--
Green and Growing


"Wizbard" wrote:

I know I should know how to do this and have probably done it before, but
can't seem to get it right:

Tables: Households (Many) Committees (One)
Fields: (Standard Contact Info Fields) (Chair & 12 # fields for Members)
Many to One Join on Committees.ID to Households.Committees_ID

I want to be able to build a Committes query and form that 1) in the form
selects a name from a Households.Head dropdown list in each Member (1, 2, 3,
etc) field; 2) after selection, displays Phone and Email info beside each
Committe.Member's name; 3) stores relational data in the proper table.

I haven't done much Visual Basic, but I have a little experience with macros.

Any tips, pointers and outright solutions are greatly appreciated.
--
Green and Growing,

-wiz