T
talktobatchu
hello
as suggested by Jeff Boyce I had redesigned by Access database to
remove redundancies to make it a normalized one. The tables have all the
required fields to store the data and need help in relating them with one
another.
ctyDistrictRegion(table 1)
-----------------------
ctyDistID(county's ID)
distNo(District Number of the county)
ctyName(name of the county)
ctyRegion(region of the county)
this table basically stores all the county names and their district numbers
along with the region(border or within).
diseaseNames(table 2)
-------------------
diseaseID(number for identiying the disease)
diseaseName(name of the disease)
ctyDiseaseStatistics(table 3)
--------------------
EntryID(disease information record ID)
diseaseID(refers the diseaseNames table)
StatisticsYear(year the information is being stored for)
ctyDistrictNumber(refers the ctyDistrictRegion table)
populationCount(population for the particular county)
numberOfCases( cases reported for the disease)
caseRate(optional field, calculating the disease rate)
The above three tables of the database store information for various
diseases for all the counties in our state and for all respective years. Are
the above tables enough for storing the information and how best they can be
related (or designed) to each other for removing redundancies.
Also if I want to store the population data according to the age groups or
say, only for teen agers(need in some diseases), what extra table should be
related to the ctyDiseaseStatistics table.
thanks for any help.
talktobatchu.
as suggested by Jeff Boyce I had redesigned by Access database to
remove redundancies to make it a normalized one. The tables have all the
required fields to store the data and need help in relating them with one
another.
ctyDistrictRegion(table 1)
-----------------------
ctyDistID(county's ID)
distNo(District Number of the county)
ctyName(name of the county)
ctyRegion(region of the county)
this table basically stores all the county names and their district numbers
along with the region(border or within).
diseaseNames(table 2)
-------------------
diseaseID(number for identiying the disease)
diseaseName(name of the disease)
ctyDiseaseStatistics(table 3)
--------------------
EntryID(disease information record ID)
diseaseID(refers the diseaseNames table)
StatisticsYear(year the information is being stored for)
ctyDistrictNumber(refers the ctyDistrictRegion table)
populationCount(population for the particular county)
numberOfCases( cases reported for the disease)
caseRate(optional field, calculating the disease rate)
The above three tables of the database store information for various
diseases for all the counties in our state and for all respective years. Are
the above tables enough for storing the information and how best they can be
related (or designed) to each other for removing redundancies.
Also if I want to store the population data according to the age groups or
say, only for teen agers(need in some diseases), what extra table should be
related to the ctyDiseaseStatistics table.
thanks for any help.
talktobatchu.