David

Are you using this combination of forms for data entry? I would personally advise against that. What you are describing works very well to display the information related to a survey and all its associated information.

To help you further, we need to see more details.

Yes. I am using them for data entry - and for display. Ill attach some images.

This shows the record sources for the Subforms (they are both ultimately getting data from the PropertyT (where the propertyID comes from). The last two images show the record sources for the combobox on each subform).

I have a lot of data that is like this.  It is a web of relations between Structures, Surveys, Locations, Reports, etc.  The Surveys (and some of the other items) have 1 main record/structure/project they are affiliated with, but then have multiple others that they are RELATED to. I have Tables for each main item, and then i created 1 Junction Table for each relation between two items.

I would guess, from the naming, that the SurveyXProjectPinWithNameScopeQ is referencing the SurveyXProjectJunctionT.  If so, as soon as you enter the record in one subform, the other will see it.  There is no difference in PIN's, in the junction table, unless you construct it.  A related project is a related project, whether it is "main" or "other".  Does that make sense?

Hi Matt - Yes. Thank you. So how would you do this on a form? How would you show one as a main one and then have a list of all the other related ones that you can add to?

To me, this is more of a business question.  If each survey has only one main project, you could put a main project field in the survey table.  You would then have to decide if you want the main project to also show up as a related project in the join table.

If each survey can have more than 1 main project and every project is either "main" or "other", you could put a project type descriptor in the junction table.  

Once you work out the tables to hold the data that you need, the form work become a little more clear.

Matt Hi Matt - Thank you for your suggestion.  To keep it simple right now and get the database up and running I took your suggestion.  I put a ProjectRelationshipType Field in the table, with either Main or Other as the 2 options.  Then in the subform for the projects on the Main form, I used a continuous form to select as many projects as one wants from a combo box with an additional combo box for the record to select main or related from that new field. Then if Main is selected I created an Expression under Conditional Formatting that highlights the main record in a different color to give a visual difference.  I am going to try and write code that can do what I originally wanted to do. The people I am doing this for want to keep the MAIN info in one area on the form and the RELATED on another.  This is a great solution that will work for now. I want to really thank you for the suggestion.  I am still taking classes on the site here and have way more to learn!

For that you could try putting two subforms in the main form.  The source for one would include only projects marked as "Main" and the other would include only projects marked as "related".  

Your approach, to make something functional now with plans to make it "right" later, has served me well.   I too, am still taking classes on the site here and have way more to learn.  

Thank you, Matt . I know I’ll figure it out, it’s just going to take some time.