Dear all,
I have a simple but very important database fundamental question on table relations with fixed values and its form design problem I am facing for easy data entry.
I have about 3 tables
o tbl_company
o tbl_Main_catego ry
o tbl_Sub_categor y
The Main Category table has 8 records and subcategory table has 100 records shared differently by the 8 records from the Main Category table)-one to many related
o These values from both table are definite field values and cannot change i.e. - no new entry is required. However the information that will change is the records in tbl_company table i.e. new company details will be entered and a corresponding score value will be entered in the sub tbl_Sub_categor y
o A company will have a category with its subcategory and a score assigned to the subcategory of each company..in which a sub category is related to the main category
Database performance/process expectations:
Behavior: When a new company is entered user need not have to re-enter any category + sub category infor to the new company since its pre–entered once
Form Design: Need to filter by company to see the related main and sub category values for each company.
My initial design:
First attempt:
2 Relationships:
o tbl_Main_catego ry - one side - tbl_Sub_categor y -many side
o tbl_Main_catego ry is the one side & tbl_company is the many side
Second attempt:
2 Relationships:
o tbl_company -one side tbl_Main_catego ry - many side
o tbl_Main_catego ry - one side - tbl_Sub_categor y -many side
Both the above table relations require the user to re-enter category & sub category values for each new company or vice versa.
I don’t know if this is the best way forward. .i.e. re-entering same values for each company.
Note: Once a new company is entered a score for each subcategory is entered.
Would appreciate a way forward on this:
I have gone in circles trying to come up with a workable method with the table relations and now numbed and exhausted.
I am also thinking of creating 8 tables representing the 8 main categories and have the subcategories as the field values but that will violet database design rules.
I don’t know how far I can apply the normalization rules.
Thanks in advance for any help!!!
I have a simple but very important database fundamental question on table relations with fixed values and its form design problem I am facing for easy data entry.
I have about 3 tables
o tbl_company
o tbl_Main_catego ry
o tbl_Sub_categor y
The Main Category table has 8 records and subcategory table has 100 records shared differently by the 8 records from the Main Category table)-one to many related
o These values from both table are definite field values and cannot change i.e. - no new entry is required. However the information that will change is the records in tbl_company table i.e. new company details will be entered and a corresponding score value will be entered in the sub tbl_Sub_categor y
o A company will have a category with its subcategory and a score assigned to the subcategory of each company..in which a sub category is related to the main category
Database performance/process expectations:
Behavior: When a new company is entered user need not have to re-enter any category + sub category infor to the new company since its pre–entered once
Form Design: Need to filter by company to see the related main and sub category values for each company.
My initial design:
First attempt:
2 Relationships:
o tbl_Main_catego ry - one side - tbl_Sub_categor y -many side
o tbl_Main_catego ry is the one side & tbl_company is the many side
Second attempt:
2 Relationships:
o tbl_company -one side tbl_Main_catego ry - many side
o tbl_Main_catego ry - one side - tbl_Sub_categor y -many side
Both the above table relations require the user to re-enter category & sub category values for each new company or vice versa.
I don’t know if this is the best way forward. .i.e. re-entering same values for each company.
Note: Once a new company is entered a score for each subcategory is entered.
Would appreciate a way forward on this:
I have gone in circles trying to come up with a workable method with the table relations and now numbed and exhausted.
I am also thinking of creating 8 tables representing the 8 main categories and have the subcategories as the field values but that will violet database design rules.
I don’t know how far I can apply the normalization rules.
Thanks in advance for any help!!!
Comment