Reputation: 111
I am currently working within Access 2013. I have a simple task that has been really driving me crazy these past few days, as I thought my relationships where correct. But when adding more data into the database I saw that there was a major problem.
Within the database everything is working fine between tblPersonal Information and tblPosition Applied for. The problem that I am running into is trying to successfully create the one to many relationship between tblPosition Applied for and tblOffer
I am trying to make it so that:
one person can apply to many positions (one to many)
one position that each person applies for can have one contingent offer (one to many) "the root of the problem that I am having"
Is their a field that I need to add, or create another table holding just the Personal ID to link tblPosition Applied for and tblOffer? I am really lost on this any help would be greatly appreciated.
Upvotes: 2
Views: 148
Reputation: 84
If a Position_applied_For
can have one-to-many offers, then you need to create a related field in tbl_Offer
, just as you did for the one-to-many relationship between tbl_Personal_Information
and tblPosition_Applied_For
. Change tbl_Offer.Personal_ID
to tbl_Offer.Position_Applied_For
and relate it back to tblPosition_Applied_For.ID
.
Upvotes: 1
Reputation: 442
Right now there are no fields that are related except Personal_ID
in the offers and applied tables. Essentially, there would be no way to distinguish if Person A applied for Job 1 and Job 2, and received an offer for Job 2.
In your tbl_Offer
, there should be a Position_ID
that relates to the Position. Also, assuming that the offer is only valid for one person, there is no need for tbl_Offer
to contain a Personal_ID
field, as it would be related through the tblPosition_Applied_For
.
Upvotes: 0