Lee,
the extra info is most helpful.
I will outline how I think the tables need to be set up to make best use of
Access' relational features.
To protect your existing data, make 2 backup copies of all 3 tables before
you make any changes to your tables.
While making changes to tables, always keep at least one backup that you
never destroy - then it is always there for reference if something goes
wrong.
tblClientList
ClientD >> Primary Key
Client Name
other client details
tblContacts
ContactID >> Primary Key
ClientID >> Foreign Key
other contact details
In the relationships window, drag the ClientID from tblClientList and drop
it on the ClientID in tblContacts.
tblFunctions
FunctionID >> Primary Key
other function details
tblAttendance
AttendanceID >> Primary Key
ContactID >> Foreign Key
FunctionID >> Foreign Key
other details about attendance
In the relationships window, drag the ContactID from tblContacts and drop it
on the ContactID in tblAttendance.
Drag the FunctionID from tblFunctions and drop it on the FunctionID in
tblAttendance.
tblAttendance allows multiple contacts to attend multiple functions.
There is a many to many relationship between Contacts and Functions
You will need to re-design your forms.
Here is a description of how to set up forms for a many to many
relationship.
Use a main form (single view) for one of the Many side tables. Within the
main form, use a continuous subform bound to the junction table with the
Link Master set to the main form's PK field. This subform has at least one
visible control that is a combo box bound to the second table's PK field.
This form's Current event and the combo's AfterUpdate event sets an
invisible text box on the main form to the value of the combo box.
Along side the continuous subform is another subform bound to the other many
side table with its Link Master property set to the invisible text box.
With this arrangement, you can navigate or search for the main form record.
The continuous subform displays the items assigned to the main form record.
Clicking on a record in the continuous subform automatically displays the
related
record in the other subform.
You'll find an example of a subform used in this way in the sample Northwind
database which comes with Access. In that the Orders Subform is based on
the
Order Details table (the subform actually uses a query, but that's
immaterial
to this issue) which models the many-to-many relationship between Orders and
Products. In the subform a combo box is bound to the ProductID column,
which
is the foreign key referencing the key of the Products table. The combo box
is set up in the way described above to show the name of the product,
hiding the ProductID which is its actual value. It also shows a
Discontinued
column in its list, but that's immaterial to the current issue.
Good luck
Jeanette Cunningham
Hi Jeanette... I'm finally getting back to this. Thanks for responding.
I'll
[quoted text clipped - 71 lines]