forms & subforms

[bfence]

Hi! I'm trying to figure out if there's a way to set up continuous
forms and sub-forms. I know it's not technically possible but
hopefully there's a work around.

My forms are:
Characteristics - main form one record per teacher candidate
Candidacy - could be multiple records per candidate
Student Teaching - could be multiple records per candidate per
candidacy record
Placement Choices - one record per Student Teaching record
Field Experiences - multiple records per candidate per candidacy
record

Primary & Foreign Keys:
Characteristics: UIN (pk)
Candidacy: CandID (pk), UIN (fk)
Student Teaching: STID (pk), CandID (fk)
Placement Choices: PlaceID (pk), STID (fk)
Field Experiences: FEID (pk), CandID (fk)

What I'd like to be able to do is open the Characteristics form and
see how ever many Candidacy records a particular teacher candidate has
- for example, one record for Elementary Ed, one record for Early
Childhood. Depending on which Candidacy record I'm interested, after
selecting it, I'd like to see the other associated data from the other
forms.

Is there a way to accomplish this? Any advice would be greatly
appreciated!

Betsy

 

[Ken Sheridan]

Betsy:

It is possible to correlate continuous form view subforms. Its done by
including a hidden unbound text box in the parent form whose ControlSource
references the primary key of the 'referenced' subform and then making this
the LinkMasterFields property of the 'referencing' subform.

So, if you have a continuous subform for candidacy within a single form view
characteristics parent form, linked in the usual way, you'd include a hidden
text box in the parent form, txtCandID say, with a ControlSource property
along these lines:

=sfcCandidacy.Form.CandID

where sfcCandidacy is the name of the subform control i.e. the control in
the characteristics parent form's Controls collection which houses the
candidacy subform.

The LinkMasterFields and LinkChildFields properties of a student teaching
continuous subform, also in the parent characteristics form, would be
respectively:

txtCandID
CandID

You could then correlate a placement choices subform with this by having a
hidden text box txtSTID in the parent form with a ControlSource:

=sfcStudentTeaching.Form.STID

The LinkMasterFields and LinkChildFields properties of the placement choices
subform would then be:

txtSTID
STID

A field experiences subform could be correlated with the candidacy subform
in the same way as the student teaching subform, with LinkMasterFields and
LinkChildFields properties of:

txtCandID
CandID

If you are including all these subforms in one parent form, if each is
likely to include more than handful of rows at any one time you might
consider putting them on separate pages of a tab control to avoid cluttering
up the form unduly.

Ken Sheridan
Stafford, England

 

[bfence]

Betsy:

It is possible to correlate continuous form view subforms.  Its done by
including a hidden unbound text box in the parent form whose ControlSource
references the primary key of the 'referenced' subform and then making this
the LinkMasterFields property of the 'referencing' subform.

So, if you have a continuous subform for candidacy within a single form view
characteristics parent form, linked in the usual way, you'd include a hidden
text box in the parent form, txtCandID say, with a ControlSource property
along these lines:

=sfcCandidacy.Form.CandID

where sfcCandidacy is the name of the subform control i.e. the control in
the characteristics parent form's Controls collection which houses the
candidacy subform.

The LinkMasterFields and LinkChildFields properties of a student teaching
continuous subform, also in the parent characteristics form, would be
respectively:

txtCandID
CandID

You could then correlate a placement choices subform with this by having a
hidden text box txtSTID in the parent form with a ControlSource:

=sfcStudentTeaching.Form.STID

The LinkMasterFields and LinkChildFields properties of the placement choices
subform would then be:

txtSTID
STID

A field experiences subform could be correlated with the candidacy subform
in the same way as the student teaching subform, with LinkMasterFields and
LinkChildFields properties of:

txtCandID
CandID

If you are including all these subforms in one parent form, if each is
likely to include more than handful of rows at any one time you might
consider putting them on separate pages of a tab control to avoid cluttering
up the form unduly.

Ken Sheridan
Stafford, England

Thanks Ken! I'll give this a shot!

Betsy