Forum Discussion
QuickBaseCoachD
6 years agoQrew Captain
My suggestion is to change the structure of your app.
It should be set up like
One Course Master has Many Scheduled Courses.
The Course Master is like the catalogue of the course content.
The Scheduled Course is saying that say Economics 101 will be run in the Fall 2018 semester.
Then One Scheduled Class will have many Student Class Registrations.
One Student will have Many Student Class Registrations.
It should be set up like
One Course Master has Many Scheduled Courses.
The Course Master is like the catalogue of the course content.
The Scheduled Course is saying that say Economics 101 will be run in the Fall 2018 semester.
Then One Scheduled Class will have many Student Class Registrations.
One Student will have Many Student Class Registrations.
- RuelYparraguirr6 years agoQrew TraineeThank you for your fast reply. I will try this one out. But will a simple summary field and lookup not work out?
- QuickBaseCoachD6 years agoQrew CaptainThe problem is that presumably you do not want to spend the rest of your life adding a new summary field every time there is a new scheduled class which has a unique start date. That would be the only way to get a count of the # of students for a given start date. But then every new Course Start date will need to have a new summary field, so that is not a correct design.
- RuelYparraguirr6 years agoQrew TraineeGot it. Thank you so much.
- RuelYparraguirr6 years agoQrew TraineeHello. Just a follow up question. In the set up above, how many tables were on it?
- QuickBaseCoachD6 years agoQrew CaptainThere are 4 tables.
1. Course Master
2. Scheduled Courses
3. Students
4. Student Class Registrations