First of all, thank you for your reply. However, I feel that the answers you provided may not be optimized for what I am currently trying to implement.
I would like to ask if there is a better way to run it with toolset after looking at the following explanation.
What we're trying to implement is exactly.
1. Register member information on the backend. Membership information includes: (name, gender, country, year/seminar, e-mail)
2. Membership information of the matching backend can be inquired by searching for the above items (name, gender, country, year/seminar, e-mail) at the front end. (Refer to the image I attached at the first question)
3. There are events for each year. When selecting a year on the search form, I hope that you can only select events belonging to that year.
4. When searching finally, matching member information will be displayed along with information such as (name, gender, country, year/seminar, e-mail).
When implementing the above function using toolset, I would like to ask you which method is the most appropriate.
I'm sorry. There are many things I don't know, so I ask you one by one. I am asking because I think it will be difficult to register and manage member information with the relationship method. (There are currently approximately 3,700 member information required to register.)