Simon,
This question is just too "broad" to be answered in a newsgroup/email
environment. It would probably take a responder several pages to cover the
concept of One to Many Relationships.
Please see "one-to-many relationships" in Help.
Specific questions, with details, are your best bet for a response...
hth
Al Camp
Use a Form for the "one" side of the relationship, with a Subform for
the "many". The "one" side table should have a unique FamilyID (*not*
a name since names are not unique), and the Subform should be based on
a table with a "foreign key" field of the same datatype. The Subform
control would have FamilyID as the Master and Child Link Field
property.
By joining two tables using either a different number of fields, or
trying to join two fields of different datatypes - such as joining an
Integer to a Text field.
Join on a single field or several fields, joining fields of the same
datatype.
One possible problem: if you have Lookup fields in your table and try
to join two tables joining by a Lookup field, it won't work as you
expect. The Lookup misfeature CONCEALS the actual content of your
database (usually a Long Integer ID field) - it *looks* like you have
Text but you don't.
What field are you trying to join? WHat field are you joining it to?
What are the datatypes of these fields?
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
