neilwebber
Registered User.
- Local time
- Today, 04:53
- Joined
- Aug 19, 2002
- Messages
- 35
Hi All
First - hope I'm in the right forum here.
I know that normalisation is already well covered here (not least by Pat) but I can't find anything that addresses my particular question.
I have a large db (50-60 fields, mostly Yes/No).
Field 'PCLNo' is PK and represents a geographical location. All other fields contain info relating to that specific location.
The info is presented on several tabbed forms and each form must cycle thru with one record = one 'PCL Number' ie the user always wants to find the site (PCL No) and then view or edit the info for that site.
There are some 'repeating groups' - PA1, PA2 etc (see Pats 1st book extract) so I know that normally I should split these from the big table and have PA1 etc as PK and PCLNo as foreign key. However, how do I then put these details on a form so that they all appear under 1 PCLNo record rather than the form cycling thru each PA? Is this what subforms are for?
Basically what I'm saying is if I split the table into several smaller ones I'd still always want PCLNo as the PK as every other piece of data always relates to this number, and would have a series of 1:1 relationships. So, is it worth normalising or should the db remain flat?
I should say that the db is used for viewing and update only, no analysis or calculations are performed and is very rarely searched - users generally know what 'PCLNo' they are looking for.
Apologies if I haven't expressed this very well - I'm probably missing something obvious but I've been thrown in at the deep end somewhat (management eh?)
thanks
First - hope I'm in the right forum here.
I know that normalisation is already well covered here (not least by Pat) but I can't find anything that addresses my particular question.
I have a large db (50-60 fields, mostly Yes/No).
Field 'PCLNo' is PK and represents a geographical location. All other fields contain info relating to that specific location.
The info is presented on several tabbed forms and each form must cycle thru with one record = one 'PCL Number' ie the user always wants to find the site (PCL No) and then view or edit the info for that site.
There are some 'repeating groups' - PA1, PA2 etc (see Pats 1st book extract) so I know that normally I should split these from the big table and have PA1 etc as PK and PCLNo as foreign key. However, how do I then put these details on a form so that they all appear under 1 PCLNo record rather than the form cycling thru each PA? Is this what subforms are for?
Basically what I'm saying is if I split the table into several smaller ones I'd still always want PCLNo as the PK as every other piece of data always relates to this number, and would have a series of 1:1 relationships. So, is it worth normalising or should the db remain flat?
I should say that the db is used for viewing and update only, no analysis or calculations are performed and is very rarely searched - users generally know what 'PCLNo' they are looking for.
Apologies if I haven't expressed this very well - I'm probably missing something obvious but I've been thrown in at the deep end somewhat (management eh?)
thanks