Forum Discussion
MarkShnier__You
Qrew Legend
You basically have two choices.
One choice is to have multiple Relationships.
So for example a field for Client Main Contact with where the relationship is [Related Main Client Contact].
Then duplicate that field which will conveniently duplicate the relationship and give you a new relationship for [Related Secondary Client Contact].
Be sure to set a correct "Proxy" field for each contact.
The other alternative is to have a many to many join table called say Project Contacts. One Project has Many Project Contacts and One Contact is used on many Project Contacts.
The Project will have an embedded child table of Project Contacts.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
One choice is to have multiple Relationships.
So for example a field for Client Main Contact with where the relationship is [Related Main Client Contact].
Then duplicate that field which will conveniently duplicate the relationship and give you a new relationship for [Related Secondary Client Contact].
Be sure to set a correct "Proxy" field for each contact.
The other alternative is to have a many to many join table called say Project Contacts. One Project has Many Project Contacts and One Contact is used on many Project Contacts.
The Project will have an embedded child table of Project Contacts.
------------------------------
Mark Shnier (YQC)
mark.shnier@gmail.com
------------------------------
PaulPeterson1
3 years agoQrew Assistant Captain
Thank you Mark!
I used the first approach once before with the contacts table and thought there had to be a better way. The embedded report is not an option as I will need to use the data in other fields as well.
------------------------------
Paul Peterson
------------------------------