How do I link several forms to one id in one table

[MaxineC]

I use the data base to record details of students I see. I currently have 1
table with one main form and several other forms that are accessed from
command buttons on the main form. The forms accessed by the command buttons
have a series of option buttons which help me record issues the child has.
How do make the information recorded on each of the forms relate to the child
and information on the main form.
Hope that is clear. Thanks

 

[Rod Plastow]

Hi Maxine,

It seems the best way to solve your problem as asked is to make the "several
other forms" subforms on the main form and let Access perform the
synchronization. If you want to see more than one subform simultaneously
then include more than one subform. If not consider: overlaying the subform
controls and making the appropriate one visible according to the command
buttons on the main form; or having just one subform control and changing the
source (i.e. the subform) that it displays.

But ...

.... you mention you only have one table! This suggests to me you are
displaying different fragments of the same record and not a parent-child
table relationship that is typical of main/subform functionality. If this is
the case why not consider putting the data from "the several other forms" on
a tab control?

Respond if you need help with either of these suggestions .

Rod

 

[John W. Vinson]

I use the data base to record details of students I see. I currently have 1
table with one main form and several other forms that are accessed from
command buttons on the main form. The forms accessed by the command buttons
have a series of option buttons which help me record issues the child has.
How do make the information recorded on each of the forms relate to the child
and information on the main form.
Hope that is clear. Thanks

I suspect that the root of the problem is an incorrect table design. Do you
have one field for each issue? If so, you're "committing spreadsheet upon a
database", a misdemeanor.

A better structure would be a table of Students; a table of Issues; and a
third table with fields for the StudentID and the IssueID, along with any
other fields needed to record information about *this* issue as it pertains to
*this* student.

What in fact is the structure of your tables?

John W. Vinson [MVP]