Y
Yam84
Hello,
I have a question related to parent-child relationships. I am
designing a system that will be used to keep track of released
materials. I am working on the design at this point and ran into what
may be a design issue.
Each job number will have many releases, many releases will belong to
one and only one job
Each draftsmen will have many material releases; Many materials will
be released by one and only one draftsmen.
Each Material release will have one requisiton which represents that
release, One requisition will represent many material releases.
Using this logic, I created my relationship like this:
TBLRequisition:
reqID (PK)
reqReleaseNo
reqReleaseDt
reqRequiredDt
statusId
reqComments
reqQuantity
matRelId
jobNumber
jobSiteId
TBLMaterialReleases
matRelID (PK)
delivTypeID (FK)
finishID(FK)
matDesc
matQty
matDetailReq
matComments
hwTypeID(FK)
matPieceMk
jobNumber(FK)
empID (FK)
reqID (FK)
TBLProjectInformation
jobNumber (PK)
jobName
plantlocation
empID (FK)
jobSiteID (FK)
My question is this: My understanding of relationships indicate that
you have to have a parent record, and then a record will be created in
the child table cooresponding to that parent. To me, it looks like
that child in the relationship (Material releases-the many side)
should be the parent and the parent (Req-The one side) the child, due
to the fact that materials will need to be 'released' before a
requisition can be added to them. However I feel like if i change the
relationship to Many requisitions have one and only one release; One
release is related to many requisitions, the relationship would be
wrong.
I have a question related to parent-child relationships. I am
designing a system that will be used to keep track of released
materials. I am working on the design at this point and ran into what
may be a design issue.
Each job number will have many releases, many releases will belong to
one and only one job
Each draftsmen will have many material releases; Many materials will
be released by one and only one draftsmen.
Each Material release will have one requisiton which represents that
release, One requisition will represent many material releases.
Using this logic, I created my relationship like this:
TBLRequisition:
reqID (PK)
reqReleaseNo
reqReleaseDt
reqRequiredDt
statusId
reqComments
reqQuantity
matRelId
jobNumber
jobSiteId
TBLMaterialReleases
matRelID (PK)
delivTypeID (FK)
finishID(FK)
matDesc
matQty
matDetailReq
matComments
hwTypeID(FK)
matPieceMk
jobNumber(FK)
empID (FK)
reqID (FK)
TBLProjectInformation
jobNumber (PK)
jobName
plantlocation
empID (FK)
jobSiteID (FK)
My question is this: My understanding of relationships indicate that
you have to have a parent record, and then a record will be created in
the child table cooresponding to that parent. To me, it looks like
that child in the relationship (Material releases-the many side)
should be the parent and the parent (Req-The one side) the child, due
to the fact that materials will need to be 'released' before a
requisition can be added to them. However I feel like if i change the
relationship to Many requisitions have one and only one release; One
release is related to many requisitions, the relationship would be
wrong.