Prev: Append Query and Autonumbering
Next: Conversion To Acc2007 or beyond Suggestions ?
From: BruceM via AccessMonster.com on 24 Feb 2010 13:10
I missed that one. It would change what I said. However, if there is one
disposition per suspect per incident, I think disposition would be a field in
tblIncidentSuspect. You could (and probably should) have tblDisposition as a
lookup table, and store the key field in tblIncidentSuspect. If there could
be more than one disposition (e.g. hospitalized, then arrested) you would use
a junction table such as I showed for ForceUsed in my previous posting. In a
similar vein, in my previous posting I assumed there could be more than one
type of force used, which is why I suggested the junction table rather than a
single field.

Lee Ann wrote:
>Thanks Daryl and Bruce for your quick response(s).
>
>For Bruce, would your comment on the disposition still be true if there is
>more than one suspect, both of them having a different disposition (i.e., two
>suspects with one going to the hospital and one going to jail) within the
>same incident?
>
>Correct - LocationTypeID is the type of locale where the incident occurs
>(bar, street, residence, etc.) and there will only be one location per
>incident.
>
>> I think Disposition is an attribute of Incident. There can be a lookup table
>> for dispositions, but no need I can see for a junction table.
>[quoted text clipped - 100 lines]
>> >
>> >Thanks in advance.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-tablesdbdesign/201002/1

From: Lee Ann on 24 Feb 2010 14:13
Fred - You're correct that it is possible that there would be more than one
type of force used per suspect. Your description/view of the junction table
vs. table of entities is also helpful and will be useful in the future.

Bruce - Although I wasn't clear on the Force issue, the advice you
originally gave is correct for the situation and I'll keep with the
TblForceUsed.

Thank you!

"BruceM via AccessMonster.com" wrote:

> I missed that one. It would change what I said. However, if there is one
> disposition per suspect per incident, I think disposition would be a field in
> tblIncidentSuspect. You could (and probably should) have tblDisposition as a
> lookup table, and store the key field in tblIncidentSuspect. If there could
> be more than one disposition (e.g. hospitalized, then arrested) you would use
> a junction table such as I showed for ForceUsed in my previous posting. In a
> similar vein, in my previous posting I assumed there could be more than one
> type of force used, which is why I suggested the junction table rather than a
> single field.
>
> Lee Ann wrote:
> >Thanks Daryl and Bruce for your quick response(s).
> >
> >For Bruce, would your comment on the disposition still be true if there is
> >more than one suspect, both of them having a different disposition (i.e., two
> >suspects with one going to the hospital and one going to jail) within the
> >same incident?
> >
> >Correct - LocationTypeID is the type of locale where the incident occurs
> >(bar, street, residence, etc.) and there will only be one location per
> >incident.
> >
> >> I think Disposition is an attribute of Incident. There can be a lookup table
> >> for dispositions, but no need I can see for a junction table.
> >[quoted text clipped - 100 lines]
> >> >
> >> >Thanks in advance.
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/Forums.aspx/access-tablesdbdesign/201002/1
>
> .
>
First  |  Prev  | 
Pages: 1 2
Prev: Append Query and Autonumbering
Next: Conversion To Acc2007 or beyond Suggestions ?