1 of 1 people found this helpful
As you have said, a Group comprises many Clients. If, however, a Client can belong to more than one Group then you have a many-to-many relationship to deal with. The usual method is to create a join table, called client–JOIN–group or some such. This join table needs only two fields for it to function: foreignKeyClientID and foreignKeyGroupID. This method resolves the many-to-many relationship into a pair of one-to-manys. If there is other data particular to the Join record, you might decide to have this fields as part of the Join record (e.g. the date on which the Client joined the Group), but essentially this record exists purely to set up the link between a client and a group.
OK. thanks. that actually makes sense.
You might treat "investorGroup" as your join table. You'll have to look at all the needs for each table to see if this work, but maybe:
The group of Client_Property records with the same PropertyID would form your investor group
thanks for reply. however, the investor group / client property can possibly own more than one property so i believe going your way would create a many to many.