Hello. I gave your proef kopie file a quick look. My comments: 1. I like to name my Primary key fields (what you named "Event_PrimI, for instance) and foreigner_key fields (what you named Event_2ID) differently, specially when there are many tables to relate.2. I imagine ALL Attendants are Contacts but not ALL Contacts are Attendants, if so, Events should relate to Attendants through Event primary and foreigner keys respectively and to Contacts through Events with Contact foreigner and primary keys respectively. That way, yo can create a portal in Events to create/show all Attendants for that Event, a Portal in Contacts to show all Events a contact has participated and a portal in Attendants to show all Events an Attendant has participated. Same for the rest of tables. 3. I like to name my Table Occurrences (TOs) differently, so I can check the table occurrence easily (ie:events_ATTENDANCE|pkeyname) where events is the "parent"table" ATTENDANCE is the child, and pkeyname is the field name that ties the two tables together. 4. And I like to create single table occurrences for each table and eave them alone, perhaps on Table View mode; so if I have to check on data I go to the table and do not have to remember which occurrences is the one with the data. 5. Finally, I have developed a solution for schools which does something similar to what you are after. Contact me to discuss it.