Here's a simplified example (for a customer order database...a typical use for this kind of thing) where customers can place multiple orders; it might make the Main Form/Subform thing a little clearer:
CustomerTable
CustomerID 'Primary Key
CustomerFirstName
CustomerLastName
CustomerHomePhone
CustomerStreetAddress
CustomerCity
CustomerPostalCode
...and so forth
OrdersTable
OrdersID 'Primary Key
CustomerID 'Foreign Key
OrderDate
MethodOfPayment
...and so forth
Notice that the Tables 'cascade.' The Primary Key of the first Table becomes the Foreign Key of the second Table. Since all of your subordinate Tables are in a one-to-many relationship with the first Table, you'd simply repeat this in the same manner as the OrdersTable in the example for each additional Table.
To display all of these in one Form and to be able to enter New Records or Edit Existing Records in all of these Tables:
- The Main Form would be based on the CustomerTable
- The first Subform would be based on the OrdersTable and linked to the Main Form by the CustomerID
- Each additional Subform would be based on their own Table and linked to the Main Form by the CustomerID
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007