Jeffrey,

This is a common structure for NAF information. There are many programs written to store family information on the NAF side of the house (see Rectrac and Golftrac for examples). Most often it is:

Sponsor table:
Last Name
First Name
MI
Primary_ID
SSN
*etc

Family Table:
Last Name
First Name
MI
Primary_ID
Foreign_key (matches Primary_ID on sponsor table)
Type:
1 = Spouse
2 = Child
3 = Other (in the case where the sponsor is legally responsible for a parent)
Active:
.T. or .F. (.F. is for prior spouses and deceased children and spouses, etc and children that are >18 years of age or no longer in Sidpers)
ADuty:
.T. or .F. (is the spouse active duty - as you know only ONE can be the sponsor and it is the highest ranking or lowest ssn)
*etc

Sometimes records that have active set to false are moved to an archive table but not usually because in the case of ice rinks, gyms and bowling centers that allow for non-military and non-family members to attend they want to keep the information of non-active also.


>Can anyone recommen the best way I can relate the following tables:
>
>Soldier table - soldiers data
>Spouse table - soldier's spouse
>Dependent table - soldier's children table
>
>Soldiers can have only 1 spouse and multiple dependents. Any ideas on how I can put them all in one view?