3
Contributors
5
Replies
6
Views
10 Years
Discussion Span
Last Post by temiromi
0

A couple of suggestions

1. Ensure all tables have a PK
2. Merger EMPLOYEE with EMPLOYMENT DETAILS, they have the same pk and are 1 to 1. You could have separate tables if an employee held multiple positions over time
3. Link ACCOUNT to CUSTOMER, the customer has an account, the account has an account type

And some questions

1. Are accounts of 1 or more types?
2. Do branches have ID values?

0

thanks!

p.s.

1. yes. an account can have more than one account type.

2. no. they have branch name as their primary key.

0

1. In that case have a table called AccountType table as a lookup of the different types of account and a CustomerAccountType table to join from Account to AccountType

2. Then you have the correct detail there, however I would never allow this in a real world situation, names change but a PK should never change


Good luck with the rest of it

Cheers

D

0

I would like to do something similar but with different names and references can you help me out cos I am new in the system (database)

it me ur co project builder temiromi

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.