Alan, what I typically do with phone numbers is to create two or three text fields in my customer (or other) table called, e.g. Phone1Number, Phone2Number, etc. Then I create the same number of fields for the type of phone. These are called Phone1Type, Phone2Type, etc. That way, you put a phone number in the number field, and put in type (cell, home, work, etc.) in the type field. Some people use their cell phone as their main phone, for others it's work, others home, etc. So this way you can put in whatever numbers that person uses, and identify the type of phone in the PhoneType field. I find this more flexible than creating fields like HomePhone, WorkPhone. Hope this helps.

---

Reply from Richard Rost:

Of course, if you want to get crazy, you could set up a completely separate PhoneT table that has:

PhoneID - primary key
CustomerID - foreign key
PhoneNumber - text
PhoneType - foreign key to a type table

Then embed this in the customer form as a subform and you can have as many phone numbers for each customer as you want. This deals with setting up multiple RELATIONAL tables, which we'll cover in the first Expert class (or Access 201 if you want to look at the old lessons).