![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
I am building a database for a school. Most of my experience has been with "one to many " relationships in databases. In this scenario each student may have more than one parent, guardian and or relative. However each parent, guardian or relative could have more than one student at the school as well. This looks to me like a "Many to Many" type of situation requiring a junction table. Is there any other way that this should be approached? Or would a "many to many" be the right way? Also how do I handle data entry forms for a "many to many"? Thanks for any help I can be reached at jemadison_2000 (AT) yahoo (DOT) com |
#2
| |||
| |||
|
|
With a many to many, you can handle the data entry for your junction table like this: Create a form that updates the junction table. The field that updates the child can be replaced with a combo box that looks up in the child table. Change the form properties to have the form's default mode to be the list mode. (looks like a table). Now create a form that updates the parent. Drag the junction form onto the parent form. Presto. You can now add children to the Parents by selecting from the dropdown. "JE Madison" <jemadison_2000 (AT) yahoo (DOT) com> wrote in message news:3F430028.ABC5CD6A (AT) yahoo (DOT) com... I am building a database for a school. Most of my experience has been with "one to many " relationships in databases. In this scenario each student may have more than one parent, guardian and or relative. However each parent, guardian or relative could have more than one student at the school as well. This looks to me like a "Many to Many" type of situation requiring a junction table. Is there any other way that this should be approached? Or would a "many to many" be the right way? Also how do I handle data entry forms for a "many to many"? Thanks for any help I can be reached at jemadison_2000 (AT) yahoo (DOT) com |
![]() |
| Thread Tools | |
| Display Modes | |
| |