Garren.Shannon
Member
- Local time
- Today, 02:53
- Joined
- Sep 22, 2022
- Messages
- 113
Hello all,
I am crafting a ridership database. The database collects data about bus trips and reports totals to the state on a set annual cycle multiple times a year. Those dates change from year to year depending on the dates the calendar committee set for the coming year so I added a "SchoolYrDates" table (see below)
I run queries against the "current" dates and trigger reports for the year so obviously there can only be one "current" date set. But there are instances where the team needs to dig back in time for a report so my thinking was they could simply change the "current" flag to an earlier set... which does not feel right to me... so the question is two fold.
I am crafting a ridership database. The database collects data about bus trips and reports totals to the state on a set annual cycle multiple times a year. Those dates change from year to year depending on the dates the calendar committee set for the coming year so I added a "SchoolYrDates" table (see below)
I run queries against the "current" dates and trigger reports for the year so obviously there can only be one "current" date set. But there are instances where the team needs to dig back in time for a report so my thinking was they could simply change the "current" flag to an earlier set... which does not feel right to me... so the question is two fold.
- If I continue using a flag to mark the current date set, how should I ensure the ONLY one record set of all the future date record sets is flagged as current?
- Is there a better way to do this other than flagging the current set of dates by using a "Current Yes/No" field?