Hi I have done a ER but when I started to decompose the relationship I got so many table that now I am not sure whether it is correcr.

Please could you have a look ar it and say what you think?

Some backgound
(coursework) The database is for a Driving Licence Examination Organisation , this company will take candidates from an organisation an examine them for a specified type of Licence.



Can_Add = Candidate Address same for Ex_Add = examiner Address.

thanks for your time.
The Prophet

here is the picture http://www.profetas.greatnow.com/

The number of tables is not your problem.

There appear to be some conceptual flaws in your model.

Please tell me what

Your course assignment structure doesn't appear to work.

Your examiner structure doesn't seem to work.

Explain the relationships connected to Course.

ie. One Course has One Examiner, One Examiner has Many Courses.

ho yes, because I thought that one course may be examined by many examiners, So I had many to many relationship.

to decompose it (the table name may not be right) I created Examining.
a group of examiner assigned to a examining team. the same for candidates. a course could have many candidates , a a candidate many course so, I created a intermidiate table, assigned candidates. is that right?

You've got your many to many relationships backwards.

Course(CourseID, attributes)

Examiner(ExaminerID,Attributes)

CourseExaminer(CourseID,ExaminerID)

1 Course has Many Course Examiners
1 Examiner has Many Course Examiners.

This is probably the same problem with Assign.

Yes but it is no longer many to many. now it is , many to one. I don't know.
What would you do?

It is still many to many resolved with an associative entity.

http://www.utexas.edu/its/windows/da.../refining.html