I've just returned from a job interview (little admin job) in which I was asked to add the following tables into this existing database:
Tbl_Department (I dont think this table is relevent to this problem)
Dept_ID - PK
Tbl_Programme (this is a University Course (EG Law/Business)
Programme_ID - PK
Dept_ID - FK
Tbl_Student (this contains all the student information)
Student_ID - PK
Programme_ID - FK
The relationship works as one department has many programmes, one programme contains many students.
The problem I was given was that I was asked to add the following table
Tbl_Module (each programme has many modules, for example the programme Law would contain Contract Law, Criminal Law, Constitutional Law etc etc as modules).
Module_ID - PK
Programme_ID - FK
I thought this was simple so I attempted to create a relationship between the Module and Programme table. I realise now that this is probably not how it is suppose to be down.
Further problems will arise when they asked me to create another table that contained all the grades each student has recieved for each module - ARGH!
Needless to say I doubt I'll be getting a phone call tomorrow telling me I have the job.
I have another interview with the same company in two weeks for a similar role so I really need to get this problem sorted.
Any help you could offer would be most appriciated.
this will let you have a Many Module to Many Programme
hope this help
See clear as mud
the aim is store once, not store multiple times
Remember... Optimize 'til you die!
Progaming environment: Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010 VB based on my own environment: vb6 sp5 ASP based on my own environment: 5.6 VB-NET based on my own environment started 2007 SQL-2005 based on my own environment started 2008 MYLE YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.