No, that is the wrong structure.
You need 3 tables: one for person, one the the interviews, and one for the
interviews:
Client table (one record per person):
ClientID AutoNumber primary key
FirstName Text
LastName Text
ApplicationDate Date/Time (when person first applied for an interview)
...
Interviewer table (one record per interviewer):
PersonID AutoNumber primary key
FirstName Text
LastName Text
...
Interviews table (one record for each interview):
ClientID who was interviewed
InterviewerID who conducted the interview
InterviewDateTime when the interview was conducted.
You can now have as many or as few interviews as you need for any person,
with any interviewer, and sort them by the InterviewDateTime. You can also
do other stuff such as querying how many times a person has been
interviewed, count how many interviews each interviewer conducted in a
month, and heaps more.
Whenever you see repeating fields such as InterviewID1, Interviewer2, ...,
it *always* means that you need a related table with one column to hold that
info, instead of repeating fields in one table.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"jim Bob" <fr****@gmail.com> wrote in message
news:4B****************@news.uswest.net...
Hi, Can someone help with a simple query?
I have a table with the following.
[maintable]
Firstname
Lastname
InterviewerID1
InterviewerID2
InterviewerID3
..
InterviewerID9
InterviewerID10
In another table I have:
[Interviewer]
InterviewerID
InterviewerName
when I create a query to show the full name with all the interviewers, I
need to add the Interviewer table 10 times. Is this correct?
I have a feeeling it is coz it worked initially. Then as the data
increases, it takes forever to return the results..
I have indexed the tables etc so at a lost as to why it takes almost
forever to return.