Prepopulating(?) fields in form question

[PMCoord]

Hello!

I have a question about repopulating fields in forms that I think involves a better understanding than I currently have about row source/columns.

Details
I have three tables.
The first table is Recruits, which contains recruit information:
-StudyID (creates 1 to 1 relationship with second table)
-FirstName
-LastName
-Email address
-Department

The second table is ParticipantData, which contains various participant information (basically this is a subset of people we recruit, who become participants in our study):
-StudyID (foreign key)
-SchoolID (creates 1 to many relationship with third table)
-Phone
-ComputerOS
-ITManager
-Completed
-Group
-RV1Monitors
-RV2Monitors
-Travel times
-Subject notes

The third table is InteractionRecords, which contains details about interactions with participants:
-Record (PK)
-SchoolID (FK)
-ContactType
-ContactDate
-Status
-RVDate
-RVTime
-RVNotes

I’m trying to 1) create a Participant Data Entry Form where I can create a new record using the form and then by putting in the StudyID, prepopulate the Recruits fields into the form and then type in the rest of the fields found in the ParticipantData and 2) create an Interaction Data Entry Form where I can create a new record using the form and putting in the StudyID prepopulates fields found in the previous two tables and then allows me to enter the rest of the Interaction details.

What additional details do I need to provide to get some feedback on this?

Thank you!!!

 

[plog]

When you have a 1-many relationship in tables, the forms you use to interact with that data should be a form/subform system (https://support.office.com/en-us/ar...any-form-ddf3822f-8aba-49cb-831a-1e74d6f5f06b).

So, if Recruits have many ParticipantData records you would have a main form based on Recruits then a subform for the Participant Data.

 

[PMCoord]

When you have a 1-many relationship in tables, the forms you use to interact with that data should be a form/subform system.

So, if Recruits have many ParticipantData records you would have a main form based on Recruits then a subform for the Participant Data.

Thanks plog! If Recruits and ParticipantData have a 1 to 1 relationship (recruits will only have ONE participant data record) can I use one form?

It sounds like, however, with the Interaction Data Entry form I will need a form/subform. I'll check that out next.

 

[plog]

You really shouldn't have a 1-1 relationship. In those instances all the data goes into the same table.

 

[PMCoord]

Is this the case even if I would like to continue to upload excel spreadsheets that will only contain information for the Recruits table?

It seemed like keeping the tables separate would make that process easier. But perhaps not.

 

[plog]

A properly structured database is a properly structured database. How your data is now, or how you will import it really isn't a consideration on the ultimate table structure.

The importation process is allowed to break some of those rules, but once the import process is complete your data should be in the proper structure.

 

[jdraw]

Can you tell us in simple plain English --no jargon-- more about what Recruits are Participating in etc.?
I think it will be clearer to you and readers if we had a look at the requirements for this database.
Until we all understand the business involved and the "issue" you are having, all we can do is guess.

Good luck.