I think you will want:
- a "Group" table, with a group ID.
- a "Meeting" table, with a meeting ID and group ID. This table would also store the group note for that meeting.
- an "Attendance" table. Each record would contain the client ID, the meeting ID, and the date.
(I'd probably store the group ID too although it's not strictly needed.)
Client -< Attendance >-< Meeting >- Group
An Attendance portal on the client layout can display the gorup note from the Meeting table.
PS: You actually did use tables before, and you're still using a relational database. It's just that pre-FM7, each table was in its own file.
i strongly believe that u cant produce that kind of info in that kind of view, with a one unique key, i suggest that u do a notes table with a person's key, where u can show and filter this kind of specific info u migh need...in order doing that, u have to link the person's id with the notes table.
helful reference: try to take a look at the contact management template which is already existed within filemaker database templates
Thanks to both of you. I will check out your ideas and see what I can make with them!
I appreciate the time and thought you put into this.