Hi Richard,
I have a couple of related questions about this lesson:

1)a)Do we make the RelativeTypeID field a Combo Box (in FamilyMemberF) - because it is a Foreign Key field in the FamilyMemberT   based on the fact that it has repeating values, that we can show ONCE each on a  Helper  Table? b)If so, then why don t we make the CustomerID field   the main Foreign Key field in the FamilyMemberT   a Combo Box, as well (like we did when we had the ContactT (MANY) to CustomerT (ONE) relationship, and CustomerID was the Foreign Key there, too - but we made it a ComboBox)? c)Why don t we just make every field with repeating values (Ex: FirstName, LastName, City) a Combo Box?   Does the potential # of options have to be limited?

2)a)If you don t leave an AutoNumber field on a Form, will new records on the corresponding Table always update  with the correct AutoNumber? b)If so, why do you need to add the  AutoNumber field to Combo Boxes, at all (if their correct value would also just transfer anyway to the Table)?

Thank you very much! - You are a very good teacher.

---

Reply from Alex Hedley:

The Combobox has to contain the Foreign Key, usually the first field, and is bound to the Control so that it gets added to the Table when a choice is made.
If you have a list of Customers
And you create an Order.
You choose a Customer from a Combo
1 | Alex
2 | Rick

Say me, and store 1 in the OrderT as the FK of CustomerID.
It won't transfer unless you tell it too.