Shawn,
I would need to know more details to be sure, but on the face of what
you have said so far, I would not have separate tables for the two
programs. I would have a field in the table for Program, and on your
data form you could have a routine to automatically allocate the Program
when you enter the age, but you could then change this if necessary in
the case of the 13-year-olds or for any other reason. For the data that
only pertains to one program and not the other, it would be a judgement
call whether you still put these fields in the same single table, or
whether you opt for a sub-classing design, where you have separate
tables just for these exclusive fields, related one-to-one to the main
table.

Signature
Steve Schapel, Microsoft Access MVP
> I need to create a student/program relationship, based on the age of a
> student.
[quoted text clipped - 7 lines]
> The tables for the children and the teen programs have to be different. The
> children's program contains extra fields that are not in the teen program.