This is great but, quick question: Maybe I missed it, but my this doesn't align with my understanding of many to many relationships. I need to see the associated entries and create relationships from either list without knowingly/directly/manually interacting with a join table. - If I were to look at the Suppliers list I would want to be able to select a Supplier row and view the associated Products. - If I were to look at the Products list I would want to be able to select an Product row and view associated Suppliers. - From either list I should be able to associate one or more items from the related list and then it the association should be immediately/dynamically visible on the other list. - If a lookup / join table is used the users shouldn't need to interact with that list. Is this possible? What is best practice for that?
![[#2024MAMA] BIGBANG (빅뱅) - 뱅뱅뱅 (BANG BANG BANG) + FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/EQsYfiPR9uM/mqdefault.jpg)
What an explanation!!. Very easy to understand the relationships . Thanks Dear.
Thank you!
This is great but, quick question:
Maybe I missed it, but my this doesn't align with my understanding of many to many relationships.
I need to see the associated entries and create relationships from either list without knowingly/directly/manually interacting with a join table.
- If I were to look at the Suppliers list I would want to be able to select a Supplier row and view the associated Products.
- If I were to look at the Products list I would want to be able to select an Product row and view associated Suppliers.
- From either list I should be able to associate one or more items from the related list and then it the association should be immediately/dynamically visible on the other list.
- If a lookup / join table is used the users shouldn't need to interact with that list.
Is this possible? What is best practice for that?
that is NOT a many to may relationship.