[AccessD] Design Question

On 2/6/07, JWColby <jwcolby at colbyconsulting.com> wrote:
> Given the possibility of having multiples, I would probably have the
> individual object tables, then one big m-m "relationship" table where I
> placed:
>
> PEID
> FACID
> HDWRID
> SFTWRID
> SVCAGRID
>
>
> Probably you would want other info about the relationship such as when the
> relationship was established and when the relationship terminated:
>
> DteEst
> DteTerm
>
> "multiples" come from new records in the relationship table.
>
> A person assigned two pieces of software would be two records, with just the
> peid and softwareid, plus the DteEst.  When that person "turned in" the
> software, the record's DteTerm would be updated.
>
> The only issue with this kind of relationship is that one relationship could
> be terminated while another was not.  If that is possible, then each
> relationship needs to be established individually (separate records in the
> relationship table), so that you can record when each relationship was
> established and terminated.

Merci.

-- 
Bryan Carbonnell - carbonnb at gmail.com
Life's journey is not to arrive at the grave safely in a well
preserved body, but rather to skid in sideways, totally worn out,
shouting "What a great ride!"