G
Guest
I'm designing a database to record the lunch choices made by students in a
school.
A lunch register is taken in each class every morning showing what each
child chooses for their lunch from 'meal of the day' or one of 4 different
sandwiches or their own packed lunch or no lunch at all if they are absent.
The sandwich choices will normally remain the same, but might need to be
changed over a period of time.
This information will then be recorded on a database in order to produce
various reports (e.g. daily lunch numbers for the kitchen) and to keep track
of how much each student needs to pay.
The main data input will be via a form, where the class can be selected from
a drop down list, then the children in that class will appear as an
alphabetical list, with the possible choices as check boxes, so that the
person can go down the list clicking a single choice for each child. I will
also need a form to enter payments made towards each child's meals.
I have started by setting up tables called Class (ClassID, ClassName etc)
and Student (StudentID, StudentName etc.), which have a one-many relation.
When I start to consider the daily lunch choices I recognise that this is a
many-many relationship, so I'll need to insert another table in between.
However, I don't really want a table which has all the meal choices as fields
as this would make it difficult if they wish to change the menu at any stage
AND it would make a rather cumbersome table. I presume it would be better for
the daily choices to be recorded in a table with Date, StudentID, Choice.
I would be very grateful for any advice/help with this structure - the job
is currently done via an excel spreadsheet, which is proably why I'm having
difficulty visualising this in Access.
Thanks
Maliplex
school.
A lunch register is taken in each class every morning showing what each
child chooses for their lunch from 'meal of the day' or one of 4 different
sandwiches or their own packed lunch or no lunch at all if they are absent.
The sandwich choices will normally remain the same, but might need to be
changed over a period of time.
This information will then be recorded on a database in order to produce
various reports (e.g. daily lunch numbers for the kitchen) and to keep track
of how much each student needs to pay.
The main data input will be via a form, where the class can be selected from
a drop down list, then the children in that class will appear as an
alphabetical list, with the possible choices as check boxes, so that the
person can go down the list clicking a single choice for each child. I will
also need a form to enter payments made towards each child's meals.
I have started by setting up tables called Class (ClassID, ClassName etc)
and Student (StudentID, StudentName etc.), which have a one-many relation.
When I start to consider the daily lunch choices I recognise that this is a
many-many relationship, so I'll need to insert another table in between.
However, I don't really want a table which has all the meal choices as fields
as this would make it difficult if they wish to change the menu at any stage
AND it would make a rather cumbersome table. I presume it would be better for
the daily choices to be recorded in a table with Date, StudentID, Choice.
I would be very grateful for any advice/help with this structure - the job
is currently done via an excel spreadsheet, which is proably why I'm having
difficulty visualising this in Access.
Thanks
Maliplex