Mis-asked the last part.
Form on Registration, embedded report for Tickets, select the Ticket record to be updated and resume the update to the Ticket fields?
Katherine,
Would you draw a picture of the relationships? I am not following the architecture of the application.
Event - has unique date/time and associated marketing data.
Registration - one record for every participant in an event including the date/time selected from Event- child of the Event>Registration relationship
Ticket - one record for every participant in an event and includes problem statement.
I've left out a Client table in the initial description. A Client may have many Tickets, A Client may register for multiple events so actually:
Events -> Clients
Events -> Registrations
Clients -> Registrations
Clients -> Tickets
Registrations -> Tickets
parent -> child (for above reference)
Registrations are driven by an EOTI form that gets the Ticket added and, if needed, a new Client record added.
I would like to allow internal user to select the day of the event (I may be able to use use Today, have to think about that), display a list of all the Tickets specific to this Event (I can do that via a field in Tickets), view the associated problem and, optionally, update that specific Ticket record's solution field.
Qrew LegendDo you have these two relationships
Events -> Registrations
Registrations -> Tickets
There for you can lookup the value for the Record ID# of the Event [Related Event] from the Registrations down to Tickets.
Then create a Report Link field for Tickets on the Event Table by matching Record ID# on the right with the lookup of [Related Event] (which I suggest called [Record ID# of Event]. That way the Tickets for the Event will be on the Event Record itself.
Yes, I do have those two relationships.
Thank you! I'll fuss around with this to make sure I understand it :)
Also had another thought this morning that I may give a try.
