Ausm1

Raz, Thank you for all your help. I think I've mostly got it and seems like it was much simpler than I was making it. But I'm still having trouble actually making it work. I put a payment field in the Registration table. However, I can't seem to put it on any layout so that I can actually enter information into it...... I'm not totally sure what you mean by: "if you put a payment field in the registration table, you could put a portal from a Contacts layout displaying payment field from Registrations ContactID table occurence." Put a portal from a Contacts layout where? And do you mean have the portal display the payment from the "Registration ContactID table? I'm apologize if I'm being terribly dense. It all seems to make sense until I actually try doing it! Thank you for all your help and time. I appreciate it very much! -Melody

Thank you for your response. This helps clarify some, but I’m still a bit confused, if you could offer just a bit more assistance, I would really appreciate it! I've posted a pdf of the relationship graph....it's not that there's so many relationships....I'm more confused by the labeling.....like "Event Event ID" and "Event ID", etc. I just don't get how they're connected and how to add in a payment piece to the registration table and have it link to contacts and events. The Contact pays by registration...meaning there can be multiple Contact registrations for one event.....each event will have multiple registrations and a given contact could have multiple registrations for multiple events. To be more concise, each registration will have one payment for one event for one contact. But each contact and event can have many registrations. Does this make sense? With this being the case...which suggestion do you think would work best? When you say “customer table” are you referring to the “Contacts” table already in existence? Or suggesting I make a whole new customer table? Hope this makes sense! Let me know if it doesn't. Registration_Relationships.pdf

Yes, "payments are related to events and there could be many events related to contacts". The "Registrations" table is to register contacts for multiple events. It is set up as a portal in both the "Events" (Registration Event ID) view and the "Contacts" (Registration Contact ID) view. And as a tab in both views as well. I attached a pdf of both views to this post.... Thank you for your time and support! -Melody Workshop_Registration.pdf Contact_Registrations.pdf

I am attempting to edit a built in template in Filemaker Pro 7 - Template is called "Registration". It's pretty much perfect for what I need it to do except that I need it to track payments tied to contacts and to events. I know this should be fairly easy to set up and I know how to create relationships and set up portals but I am confused by how the relationships are already set up in this template. I would like to be able to: -track multiple payments for contacts linked to mulitple events -have payments show up in Contact Registration portal Right now there are three tables set up - "Contacts", "Events", and "Registrations" and there are multiple ID's which are the linking points, which is what is confusing me. Could anyone help guide me through this process? I appreciate it. I need to know where to put the payment information and how to link it. Do I need to set up a payment ID in the Registration table? Or create a whole new "payment table"? I appreciate very much any help and support! -Melody Oaks

I am currently trying to adapt the Registrations template that comes built into Filemaker 7. I would like to add a payment piece to it to track multiple payments specific to the contact and to the event. So I would like the payments to show up in the registrations portal and the events portal. To print payment reports for each individual contact and each event. I understand linking and portals and relationships but am having a hard time figuring out the relationship already built into this template. Could anyone guide me through the best way to set this up? I appreciate your time and help very much!!! -Melody