Remove Data Duplication

  • Thread starter Thread starter LM_CTS via AccessMonster.com
  • Start date Start date
L

LM_CTS via AccessMonster.com

I want to create a table to hold Department,Division,Bank, Service, and
ServiceDetail fields. There will be one Department for multiple Divisions,
Multiple Banks for each Division, Multiple Services for each Bank and so on.
Is there a way to organize this so I'm not entering the same record with one
field variation?

(Ex. Dept1, Div1, Bank1, Service1, ServiceDetail1... Dept1, Div1, Bank1,
Service1, ServiceDetail2...)

Thanks
 
I want to create a table to hold Department,Division,Bank, Service, and
ServiceDetail fields. There will be one Department for multiple Divisions,
Multiple Banks for each Division, Multiple Services for each Bank and so on.
Is there a way to organize this so I'm not entering the same record with one
field variation?

(Ex. Dept1, Div1, Bank1, Service1, ServiceDetail1... Dept1, Div1, Bank1,
Service1, ServiceDetail2...)

Thanks
Click to expand...

If you EVER have fields named Div1, Div2, Div3 in a table... your
table is WRONG. It's a spreadsheet, not a normalized table.

If you have a One (Department) to Many (Divisions) relationship, you
need two tables. In your case you should - I'd say must! - have a
table for Departments, another table for Divisions, a third table for
Banks, a fourth table for Services, and a fifth table linking Banks to
Services.

Each table on the "many" side would have a field - the "Foreign Key"
it's called - linking it to its corresponding One side table.

Get away from the mistaken idea that everything should be in one
table. It shouldn't, not in a relational database like Access!

John W. Vinson[MVP]
 
Back
Top