T
ThomasK via AccessMonster.com
I have a database that tracks trade shows. I've set up 2 tables, one is
tblVenues, one is tblEventYear. Right now I have the two tables linked by the
field EventYear. EventYear is the primary key in tblEventYear and the foreign
key in tblVenues. I have a one to many relationship with tblEventYear being
on the one side. One event year with many venues. The problem I'm having is
that one venue can have a show at the same place for several years. So, many
venues can have events on many different years. Should this be a many to many
relationship? If so, should I have a connecting table, and what would it be?
I would like to be able to keep track of the venue information over several
years, and be able to see what information has changed each year. But I dont
want to have to re-input all the venues information for each new year.
Thanks for the help.
Tom
tblVenues, one is tblEventYear. Right now I have the two tables linked by the
field EventYear. EventYear is the primary key in tblEventYear and the foreign
key in tblVenues. I have a one to many relationship with tblEventYear being
on the one side. One event year with many venues. The problem I'm having is
that one venue can have a show at the same place for several years. So, many
venues can have events on many different years. Should this be a many to many
relationship? If so, should I have a connecting table, and what would it be?
I would like to be able to keep track of the venue information over several
years, and be able to see what information has changed each year. But I dont
want to have to re-input all the venues information for each new year.
Thanks for the help.
Tom