There are several ways to selectively list the related records for your adults and children.
A filtered portal could list them using a portal filter expression. One portal for adults, one for children, each with different filter expressions.
contacts::age = "Adult" or contacts::age = "Senior Citizen"
Would be the filter expression for the adults portal.
Or you can use two table occurrences of contacts and add a extra match field that filters for one age group or another.
You might define cAdultAges as:
List ( "Adult" ; "Senior Citizen" )
With Text as the result type. Then your relationship would be:
NeighborhoodWatchForm::Address = Contacts|Adults::Address AND
NeighborhoodWatchForm::cAdultAges = Contacts|Adults::Age
Then List ( Contacts|Adults::FullName )
will return a list of all adults with a return between each value.
Substitute ( List ( Contacts|Adults::FullName ) ; ¶ ; ", " )
Lists the same names but with commas instead of returns between each name.
Thank you Phil for the detailed response. I understood the filter portal idea and don't know why I didn't think of that before.
What someone else suggested was have a calculation field to return 1 if option is either Adult or Senior Citizen and return 0 otherwise.
I then made two other calculation fields. One that only returns zero and the other only returns 1 and thats how I split up the portals.
However, I'm a little confused about the 2nd option since I have not used Lists before. I'm more confused by what you mean by the Relationship. You mean going to Manage Database then relationship and linking those fields together?
The lists might better fit the layout of your form example--especially a list of names separated by commas which can then be a horizontal row of information.
You are welcome to ask follow up questions about that option if you want to try to get that to work for you.