If you are discussing Relationships to tables then I have two
interpretations of your question, but either way you will have no
problem as long as your database is normalized.
First Interpretation: (One table with two "many" links)
tbl_student:
student_id (Unique) (1)
student_name
tbl_course:
course_id (Unique) (1)
course_room
course_name
tbl_enrollment: (the table in question)
student_id (Many)
course_id (Many)
Some people with more experience may be able to point out problems with
this, but I this is the best method of database design as far as I'm
concerned. Beign fully normalized, it reduces duplication of data,
therefore saving space. Queries can be used easily by joining the
tables to find any information you want. There are no drawbacks that I
am aware of.
Second Interpretation: (One table with two "one" links)
tbl_rental:
car_id (Many)
rent_date
return_date
renter_id
tbl_service:
car_id (Many)
service_date
service_location
tbl_car: (the table in question)
car_id (Unique)
car_make
car_model
There are no problems with this either. It's fully normalized and
having these two links won't harm the DB at all becuase the two tables
that it's joined to usually are not related, but even then it should
not be a problem (can't think of an example off the top of my head).
Now, if you're talking about adding Joins in the Query designer then
there are a lot of little pitfalls. I don't really have enough
experience to talk about. The good thing is that if you build a well
normalized relational database then you don't have to worry about these
issues very much.
Cheers,
Jason Lepack