A
allen davidson
Hi,
I'm building a database to hold information about organizations providing
training in England.
Part of the information to record is the geographical location where the
training is provided (as opposed to the physical location of the
organization).
The client has chosen to map the location at two levels.
The first level is by 9 Regions of england.
The second level is by 350 local authority Districts. Each Region contains
between 20 and 70 Districts.
There is a one to many relationship between Regions and Districts. A
District can only belong to one Region
A further requirement is that the organizations must be searchable by region
and district.
My question is how to design both the table(s)? and form for such a large
amount of information.
If I just had to map by Region then 9 yes/no fields and 9 checkboxes on a
form would suffice and I would be happy with that.
However to record all of this with yes/no fields would need 360 such fields
and would spread accross two tables (I dont like 1 to 1 relationships but I'm
willing to re-consider). The user interface would look very clumsy, in fact I
think I'm more concerned about the UI than the table deesign.
Running on Access 2007 which will probably have a SQL back end at some point
(which would take care of 255 field limit on a table).
All suggestions welcome.
NB this is not a college project, client is part of the Health Service.
Thanks
Allen
I'm building a database to hold information about organizations providing
training in England.
Part of the information to record is the geographical location where the
training is provided (as opposed to the physical location of the
organization).
The client has chosen to map the location at two levels.
The first level is by 9 Regions of england.
The second level is by 350 local authority Districts. Each Region contains
between 20 and 70 Districts.
There is a one to many relationship between Regions and Districts. A
District can only belong to one Region
A further requirement is that the organizations must be searchable by region
and district.
My question is how to design both the table(s)? and form for such a large
amount of information.
If I just had to map by Region then 9 yes/no fields and 9 checkboxes on a
form would suffice and I would be happy with that.
However to record all of this with yes/no fields would need 360 such fields
and would spread accross two tables (I dont like 1 to 1 relationships but I'm
willing to re-consider). The user interface would look very clumsy, in fact I
think I'm more concerned about the UI than the table deesign.
Running on Access 2007 which will probably have a SQL back end at some point
(which would take care of 255 field limit on a table).
All suggestions welcome.
NB this is not a college project, client is part of the Health Service.
Thanks
Allen