relationships

[Yaya in Fargo]

I have a need to have a parent table for ALL projects. The projects fall
into four kinds (WRD-Municipal-Minnesota-Local). Each kind has its own set
of criteria that I need to manage and report. It seems to me I need my
parent table with all projects and then subtables with data specifica to the
kind. Is there a way I can force the project number from parent table to
land in its kind table? OR maybe I am thinking about this all wrong and
someone can enlighten me.

 

[John Vinson]

On Wed, 13 Oct 2004 14:24:58 -0700, "Yaya in Fargo" <Yaya in

I have a need to have a parent table for ALL projects. The projects fall
into four kinds (WRD-Municipal-Minnesota-Local). Each kind has its own set
of criteria that I need to manage and report. It seems to me I need my
parent table with all projects and then subtables with data specifica to the
kind. Is there a way I can force the project number from parent table to
land in its kind table? OR maybe I am thinking about this all wrong and
someone can enlighten me.

This may be one of the very few cases where a one-to-one relationship
is appropriate. Consider having a Projects table with primary key
ProjectID and fields for the information in common to all classes of
projects; you'ld have four additional tables with ProjectID also as
the PK and the fields specific to WRD or Municipal or whatever.

These tables will not automagically fill in (and they shouldn't; you
wouldn't want a record in the Local table if it's a Minnesnowta
project). Instead, use a Form based on the Projects table, with four
Subforms, one for each project type; use ProjectID as the master/child
link field.

John W. Vinson[MVP]
Join the online Access Chats
Tuesday 11am EDT - Thursday 3:30pm EDT
http://community.compuserve.com/msdevapps