Do you know how to create and use a portal? if not, then look it up. The filemaker help system does a pretty good job of explaining portals.
Create a table, People, with at least one field, PersonID, set it up as an auto-entered serial number. Let's call your second table, addresses. Define a matching number field, PersonID in it and give it your address fields.
Link the two tables with a relationship
People:: PersonID = Addresses:: PersonID
Now you can create a layout based on the people layout and use a portal to display as many addresses are needed for this one person.
Phil, thanks for the help. Could I request one clarification? This is something that has confused me about related tables. In the solution you explained with related tables, is there one table (addresses) that will have all the address entries for every person, but just that some of them will be associated with each person?
In other words,
(a) Is there a separate instance of the "addresses" table for each record in the "People" table (somehow magically inside Filemaker), or,
(b) Is there really only one "addresses" table, with all the address entries (e.g. N1Address1, N1Address2, N2Address1, N3Address1,....) and then it knows which ones go with which record in the "People" table?
I guess it doesn't really matter as long as Filemaker keeps it all straight, but in my head I've been thinking I need something like model (a) above, and that's been confusing me. Thanks again for the help,
It's b) and this should do exactly what you need.
Thanks Phil. I think I understand now.