for Microsoft Access
Create complex MS Access databases without being an expert in relational database design! Designer for Microsoft Access asks you plain-language questions about what you want to manage with your database, and creates the tables and relationships automatically. Free trial available
Concepts >> A table is in second normal form (2NF) and there are no transitive dependencies.
A transitive dependency is a type of functional dependency in which the value in a non-key field is determined by the value in another non-key field and that field is not a candidate key.
A Practical Approach
Again, look for repeated values in a non-key field as in the following example.
The phone number is repeated each time a manager name is repeated. This is because the phone number is only a second cousin to the project number. It's dependent on the manager, which is dependent on the project number (a transitive dependency).
The ProjectMgr field is not a candidate key because the same person manages more than one project. Again, the solution is to remove the field with repeating data to a separate table.
As you've probably come to expect by now, you'll take the above table and create new tables to fix the problem.
Re-examine your tables to make sure there are no unnecessarily repeating values in non-key fields and that the value in each non-key field is determined by the value(s) in the key field(s).
That wraps up this topic on normalising to Third Normal Form. In most cases 3NF should be sufficient to ensure that your database is properly normalised, however higher normal forms can be achieved.