Yes, use a related table of email addresses.
What makes that approach seem awkward to you?
When setting up a Contacts module for a database, I frequently setup a "contact details" related table for listing all phone numbers, email addresses and social networking URL's.
I guess for some reason it felt like "email addresses" were too minor of a thing to be their own entity, and that it was more fitting for them to fall within the "People" table.
Also, if I wanted to do the same thing for phone numbers and Twitter accounts, with new tables for each, it just seemed like a basic contacts database was becoming more complicated than I expected.
But, if separate tables for each item is the correct way to go, then I can understand that.
I just wanted to make sure there wasn't some simple workaround that I was missing for situations like that.
So, I'll proceed separate with tables for:
- Email Addresses
- Phone Numbers
- Twitter Accounts
You can certainly set up a separate table for each, but if you read my last post again, you'll find that I use one related table for email, phone and social networking details. I include a "type" field to identify the type of contact detail.
When you say "type" do you mean "Work vs. Personal" or "email vs. phone vs. social networking"?
I get that you have a single table, but I'm still having a bit of trouble picturing exactly how the fields are labelled, and then how they are displayed on a layout.
Thanks for your patience...
There are various options for how to set up the table and your layout so I encourage you to experiment and use what works best for you.
I set up this relationships for this:
Contacts::__pkContactID = ContactDetails::_fkContactID
with "allow creation..." enabled for ContactDetails.
I then might define the following fields:
DetailType: text, formatted with a value list of types such as: Home, Office, Cell, Email, Social...
DetailContact: Text, the actual email address or phone number. I typically include an auto-correcting calc for phone numbers
DetailComments: A text field if I need to record any additional commentary about a specific phone, email, etc.
A single portal can list all such contact details for a given contact or I can set up multiple filtered portals that list just one type or group of types.
Ok, I get it now. Thanks very much for your help!