This is not a recommendation, but rather an option to explore:
Seems like you have two tables that store names and contact info. In one table you have names of companies and contact info and the other, the name of people and their contact info. Some database designs might thus put both in the same table. But whether or not this is the optimum design is something that relies on how you need to use these two groups of data.
Also, in this day and age, there are many ways to electronically reach a contact. I thus set up a related table with one related record for each phone number, email and social networking site that I want to record for a given contact. You may also want a related table for addresses if you have the need for more than one set of addresses for a given contact such as a company's physical address and what might be a separate billing address for corporate headquarters.
I've taken you up on the idea of creating a separate table for the addresses, and it works well.
I've learned a few more things with FM, and I'm pressing ahead with creating the database.