M
Mike
Hello,
I received some help before, but it did not address the
issue fully.
I have a form that has students as the main form, and
their parents as a subform. The link field is the
studentID, so I have a corresponding studentID in the
parents table. However, in instances where there are
sibling students, I have had to create a duplicate record
for the parent(s) in the parents table so the parents can
also relate to the sibling's studentID number. What I
would like is a way I can simply relate a sibling student
to an already existing parent record. I would also need
to retain the ability to relate more than one parent
record to a student, to accomodate multiple parents in
divorce situations.
I have created a juntion table with the studentID and
parentID as primary keys. Do I have to populate that
table with all of the data from both the student and
parent tables and then use that as the underlying data
source for the form? Or is there a better way to utilize
this many to many relationship? Please adivse.
Thanks,
Mike
I received some help before, but it did not address the
issue fully.
I have a form that has students as the main form, and
their parents as a subform. The link field is the
studentID, so I have a corresponding studentID in the
parents table. However, in instances where there are
sibling students, I have had to create a duplicate record
for the parent(s) in the parents table so the parents can
also relate to the sibling's studentID number. What I
would like is a way I can simply relate a sibling student
to an already existing parent record. I would also need
to retain the ability to relate more than one parent
record to a student, to accomodate multiple parents in
divorce situations.
I have created a juntion table with the studentID and
parentID as primary keys. Do I have to populate that
table with all of the data from both the student and
parent tables and then use that as the underlying data
source for the form? Or is there a better way to utilize
this many to many relationship? Please adivse.
Thanks,
Mike