Forum Discussion
EvanMartinez
4 years agoModerator
Hi Rachel,
When two tables need to be able to have multiple relationships between them, in your example when many Vendors could be related to many Extracts, this can be accomplished using a many to many relationship. Instead of directly relating the two tables you create a third table that sits between the two tables (we call it a join table and often name it something like Assignment). Then every time an Extract is related to a Vendor you create a record that tracks the connection, then you could have any number of instances where a Vendor or an Extract could be connected. You can even include an embedded report right on your Extracts table from the new table that sits in the middle so that a user can go in and select which Vendors should be connected to the Extract. It takes a little set up but allows consistent reporting and more flexibility in how those two tables relate to eachother.
------------------------------
Evan Martinez
------------------------------
When two tables need to be able to have multiple relationships between them, in your example when many Vendors could be related to many Extracts, this can be accomplished using a many to many relationship. Instead of directly relating the two tables you create a third table that sits between the two tables (we call it a join table and often name it something like Assignment). Then every time an Extract is related to a Vendor you create a record that tracks the connection, then you could have any number of instances where a Vendor or an Extract could be connected. You can even include an embedded report right on your Extracts table from the new table that sits in the middle so that a user can go in and select which Vendors should be connected to the Extract. It takes a little set up but allows consistent reporting and more flexibility in how those two tables relate to eachother.
------------------------------
Evan Martinez
------------------------------