Thank you so much for your kind, prompt.
I am sorry for not responding sooner.
I am writing upon reading your kind tip.
Can you kindly take a look at the screen print below and to let me know whether
I am making a right approach?
I would like to learn the best possible E-R model from the given scenario.
Thanks again!
Main Topics
Browse All Topics





by: bitter_chickenPosted on 2009-02-08 at 18:12:08ID: 23586937
Either
a) create a single entity 'people' which represents both clients and employees; or
b) create a single abstracted entity 'people', then two entities related to that... 'clients' and 'employees', then a relationship from each 'clients' and 'employees' to 'sales'
In practise, a FK on the 'clients' table, and a FK on the 'employees' table will link each record to the 'people' table, so a person can be an employee, a client, both, or neither.
The 'people' table would include standard information (such as name, address), and the 'employee'/'client' tables would have information such as employee ID.
<can be> -- 1 [Employee] 1 -------<assists>
/ \
1 / \ n
[People] [Sales]
1 \ / n
<can be> -- 1 [Client] 1 -- <purchases>