I understand the purpose of normalization.  But what about a situation like in my case.  I track surveys with access and each survey can have multiple surveyors and multiple dates that the survey was completed on.  I understand that I can pull the surveyors from a surveyor table but what about the multiple dates?  Will I have date1 date2 date3 in my survey table?  Is thee a way to get around this?  And when I make the report to show who completed that survey, how will I show the multiple surveyors if they are contained in a table singlely.  Would I just duplicate the TechID.FullName field multiple times on the report?  For example, I have survey ID carson123 which was completed in 2013 on work request 123456 by Surveyor Jon Smith on 4/15/13, Alex Jones on 4/16/13 and Josh Anderson on 4/17/13.  These surveyors will have other work requests (WR's) from previous years as well as several others from the current year.  How do would you build the tables and forms for that situtation?  I don't see how to get around making surveyor1 date1, surveyor2 date2, surveyor3 date3 etc.

---

Reply from Richard Rost:

You would have two tables: one for the survey itself and another for the surveyors and the dates they surveyed. Think of it like a class with multiple students. In your class table you wouldn't have fields Student1, Student2, Student3, etc.