Richard, that is actually what I usually do, but it's more complicated. I was trying to keep things simple, and if you know you'll only need 2 or 3 phone numbers, the other way is fine. But you're right, your way allows as many phone numbers as you want to put in. The one advantage I see to the simpler way is that, if you want to put a phone number on a report, you can assume that Phone1 will be the most important one, and you can put that in the report. If you have a separate table, it's not as easy to put a phone number in a report.

---

Reply from Richard Rost:

Absolutely correct, Greg. Simple is usually better. I personally use YOUR method myself for my business databases. I have 3 phone number fields and almost NEVER need a fourth. If I do, I toss it in the notes field.

HOWEVER, playing Devil's Advocate, it you want to specify a number as a "primary" number to be used on reports, just add a field "IsPrimary" and then check it on or off for the primary number. When you make your report, just build a query first that pulls in just the primary phone number.

But you're right... especially for a conversation related to Access Beginner Level 1. :)