Your initial challenge is to estimate with fair accuracy your future
reporting needs so that you can do proper design now. For example, it seems
commonsensical that a customer can have one or more phone numbers, one or
more email addresses, etc., and that those attributes may attach to multiple
persons at the customer address. You may want several tables to accomodate
this, particularly if your dataset is already large, or you think it will
become so. From my point of view in my work, if the dataset is not large and
won't be for a long time I would not use Access but just use Excel instead.
*shrug*
Anyway, relational database design = 1st step.
Once that's done, we can start answering questions about how to, for
example, do phone number lookups in subforms (the many side of the
one-to-many relationships mentioned above).
