Are you wanting a contact book where each person can have one and only one phone number, email, etc? If so a single table should be fine.
If you want to be able to list a Work phone, Home phone, Mobile phone, etc, you want one table that has the 'person' information and another that holds Phone Numbers. You can make the same table hold multiple Emails but you're better off with two subtables.
The way you connect them is through the Relationships screen and your table design. You Main table will have a Primary Key field (usually autonumber type). Your subtables will have their own, separate PK, but also what's called a Foreign Key field. If the PK is Autonumber, the FK should be Long Integer. Draw a line from the Main table PK to the FK in the Phone subtable, and you should get a prompt for making a One-to-Many connection between the two. Repeat as needed for Email table.
The other thing you'll want in your subtable is a field to tell you what Method of contact it is. Comboboxes work well here: "Work", "Home", "Mobile", etc.
Your Form, then, will have the Main information, but also a subform (or two) that shows all Phone Numbers associated with that particular Main PK. Let the subform wizard do the heavy lifting here.
Good luck! Normalization is your friend, google it and curl up with it for an hour or two to wrap your head around how relational databases differ from spreadsheets.
