In my first table, I have Projects: A, B, C. They are single select tagged as Locations 1, 2, 3. They are tagged with Persons (a Linked Table).
In my second (Linked) table, Persons. All the Projects are automatically combined into one column.
Users will input data in the first table. In the second table, I need each Location to be a column header, so that each Project is parsed across those location columns.
In short, I need the tags in the first table to be the column headers in the second table.
Projects, with fields Locations (Single Select), Persons (Linked Record)
Persons, with fields Projects (Linked Record)
What you mean?
I think you need a third table for Locations, why you didn’t make it?
Your terms does not make sense to me (tags, columns headers, etc). You have to explain your use case, which “thing” belongs to another. A Person lives in a Location? A project is made in a Location? Then you make the logic relations with Linked Records, and then you can show data from other tables via Lookups and Rollups.