K
KarenF
Hi,
I'm creating a database for someone who requires a timetable of
interpreters/note takers and helpers for disabled students attending classes
at college. I have most of this working; however, the difficulty comes when
I need to assign more than one interpreter to a student's session (which is
every time), or more than one note taker.
I have a master Interpreter table showing id, first name, last name; another
table showing id and hours of work. I have the same for note takers, with
the addition of another table showing id and subjects they take notes for.
I've created a timetable table which I'm convinced is not right. I have a
class id (which comes from a separate table showing module name, day, time,
tutor, venue etc), the student id, interpreter 1 (lookup from interpreter
table), interpreter 2 (lookup from interpreter table), remote note taker
(lookup from note taker table), electronic note taker (lookup from note taker
table), and note taker (lookup from note taker table).
I'm thinking I really ought to have a separate record for each separate
interpreter/notetaker for each session. The person I'm creating this for is
already unhappy that she's having to populate the timetable table for each
student for each class they take every week.
The end result she needs to see is a timetable for each interpreter or note
taker showing each session, venue, time etc they need to attend. The
interpreter would also need to see the name of the second interpreter working
with them (same ofr any note takers). This will be in a report.
I've successfully created queries for this - of course, I can use the QBE
grid and set or criteria. However, I've tried to create a main interpreter
form with a timetable subform, which works great when the interpreter's name
is in the Interpreter 1 column, but ignores the link with the interpreter 2
column (as I thought it would).
Any advice would be gratefully received. I've created many databases
before, but none have been as challenging as this one. When I was given this
task to do, all of the information was in 1 table and columns were hidden and
displayed in queries to provide the information they required. So, the
database owner is used to that format and can't grasp the concept of
normalisation and has never used forms - never mind forms and subforms.
I think I've been looking at this for too long, so if anyone can point me in
the right direction, I'd be really grateful.
Thanks a lot.
Karen
I'm creating a database for someone who requires a timetable of
interpreters/note takers and helpers for disabled students attending classes
at college. I have most of this working; however, the difficulty comes when
I need to assign more than one interpreter to a student's session (which is
every time), or more than one note taker.
I have a master Interpreter table showing id, first name, last name; another
table showing id and hours of work. I have the same for note takers, with
the addition of another table showing id and subjects they take notes for.
I've created a timetable table which I'm convinced is not right. I have a
class id (which comes from a separate table showing module name, day, time,
tutor, venue etc), the student id, interpreter 1 (lookup from interpreter
table), interpreter 2 (lookup from interpreter table), remote note taker
(lookup from note taker table), electronic note taker (lookup from note taker
table), and note taker (lookup from note taker table).
I'm thinking I really ought to have a separate record for each separate
interpreter/notetaker for each session. The person I'm creating this for is
already unhappy that she's having to populate the timetable table for each
student for each class they take every week.
The end result she needs to see is a timetable for each interpreter or note
taker showing each session, venue, time etc they need to attend. The
interpreter would also need to see the name of the second interpreter working
with them (same ofr any note takers). This will be in a report.
I've successfully created queries for this - of course, I can use the QBE
grid and set or criteria. However, I've tried to create a main interpreter
form with a timetable subform, which works great when the interpreter's name
is in the Interpreter 1 column, but ignores the link with the interpreter 2
column (as I thought it would).
Any advice would be gratefully received. I've created many databases
before, but none have been as challenging as this one. When I was given this
task to do, all of the information was in 1 table and columns were hidden and
displayed in queries to provide the information they required. So, the
database owner is used to that format and can't grasp the concept of
normalisation and has never used forms - never mind forms and subforms.
I think I've been looking at this for too long, so if anyone can point me in
the right direction, I'd be really grateful.
Thanks a lot.
Karen