indirect table relationship question

[Caylif]

Hello, I am just starting to learn about databases and MS Access. I have a question

I have 6 tables tblBlanks, tblPowder, tblProcesses, tblTypes, tblColors, and tblProcessCategories


tblTypes has a one to many relationship with tblBlanks through TypeID field.
tblBlanks has a one to many relationship with tblPowder through BlankID field.
tblPowder has a one to many relationship with tblProcesses though PowderID field.
tblColors has a one to many relationship with tblPowder through ColorID field
tblProcessCategories has a one to many relationship with tblProcesses

Example

Type --------> Blank----------->Powder----------------->Processes
Woodbinders 9K150TDH0Z 9K150TKH0PS WT02 9K150TKH0PS WT02-250
| |
Color Process
WT02 250


This is my question. Do I have to have TypeID field in tblPowder and tblProcess
or since tblBlank has it and its related to tblPowder and its related to tblProcess does the type follow the record?

Any help is appreciated Thanks

 

[Micron]

As long as you can create a chain/path from tableA to tableZ by connecting the PK and FK fields, you don't need to (and shouldn't) duplicate fields in other tables unnecessarily. The main danger is that values can be edited in one place but not the other(s) but it's not always avoidable. FYI - you don't have to create relationships at all for the db to work - it does facilitate query design though.

From what I can see, you should be OK thus far, but it's easy to validate by testing scenarios with queries. Looks to me like you could get all Types that have a ColorID of 1 (or whatever). However, tblTypes (and maybe others) look like they're lookup tables, which typically aren't connected to anything.

 

[Arsen01]

hi all, my name is Arsen...... I am a new member here......... )) thanks for your post , nice to meet you all here, in this web site.........