this is simple: You have several options - I am sure other forum members will add to my answer.
What I woudl do is:
3 Jon Doe
You will have to connect PersonID (make a relation) in the Manage Database View. This is a structure that allows you to assign as many Group properties as you wish to the same person.
Insert a portal into your persons-layout. Let the portal show data from the table "TABLE_GROUPPROPERTY". Make the relation such that it allows to create new records in the table "TABLE_GROUPPROPERTY". Now, you will be able to add new Group Features to each person you are currently browsing.
If you use a value list to enter the Group Names in that Portal, you can be sure to always use the same set of Group names. This prevents you from Entering "Special Clients" once and "specialClients" at an other occasion. It s important when searching data or creating reports.
(and ask for details / screenshots if you don t understand a specific aspect)
thanks for your answer! I'll try it later this week! Takes some time to figure out everything...
Following on from Marius's suggestion, I would be inclined to go one step further, and have a separate GROUPS table, linked to PEOPLE via a MEMBERSHIPS table (the join table).
3 Jon Doe
M_id P_id G_id
1 1 1
2 1 2
3 2 2
4 2 4
5 2 3
The relationships will be:
People -> Memberships <- Groups
Your portal on a "People" layout will show Memberships for the current Person, with Group data coming directly from the Groups table, i.e. the join table holds only the key values. (Although it could later hold further information about that Membership, hence the flexibility.)
Happy to provide further help if required.
This is the method I use. Your memberships is your join file, but really can have loads of information (fields) unique to each membership. You may or may not have additional table(s) with the information based on diverse types of memberships, but unless there is a compelling reason for the additions, the use of slightly 'unnormalized' data may fit well in this join file.
For example, a FAMILY is a unique group with 1+ members. These people may have a family membership in a health club, or have individual membership. I believe you can deal with both situations in the single join file.
Now things like comm & addresses can relate to groups and/or individuals... But I digress from the topic.
-- sent from my iPhone4 --