> Even for just the odd country which may apply only once or twice you should
> really be storing the name of the country in the Country_Birth table. Which
> brings us to your other question regarding relationships. The answer to that
> is that you should have a one-to-many relationship between the Country_Birth
> table and your main table, and referential integrity should be enforced.
> This will prevent the same country being inadvertently entered in the main
> table under slightly different names, which can otherwise easily happen; I
> found myself under three different names as the author of technical articles
> in one database I worked on!
>
> As regards the suburbs etc you should not really be storing the post code
> and zone in the table, only the suburb. This is because the latter two are
> determined by the former, so to store them all in the main table constitutes
> redundancy. The post code and zone columns are said to be transitively
> functionally dependent on the key, which breaks one of the rules of
> normalization. As it happens I've posted a demo of how to handle data of
> this sort at:
>
>
>
http://community.netscape.com/n/pfx/forum.aspx?nav=libraryMessages&tsn=1&tid=23626&webtag=ws-msdevapps>
> If you have records in the main table where you would not want to store a
> suburb value but still need to know the post code etc, there should be rows
> in the Suburbs table for each post code with a Suburb value of 'N/A' or
> similar. You then simply select the relevant row with the value 'N/A' for
> the post code relevant to the main table's record. You don't need to include
> an 'N/A' row in the Suburbs table for all possible post codes from the start
> of course; you can add them as necessary.
>
> Ken Sheridan
> Stafford, England
>
> "Roger Bell" wrote:
>
> > Ken, I have noticed that if you type a Country not on the list, you now get
> > the option of adding or not. If this is just an odd one that you want in the
> > record but not added, when you answer "no" it will not accept this odd one, I
> > guess because you have to set the properties "Limit List" to yes. Is there
> > any other way around this?
> >
> > Secondly, I have also tried the Form option on another combo field which has
> > the row source to a table called "Postcodes" which has 3 fields: Suburb,
> > Pcode & Zone. At present when the Suburb is selected the corresponding pcode
> > and zone is automatically entered by way of an Afterupdate event procedure. I
> > am not sure what info I need to show in the line "If Not is
> > Null(Dlookup(:CityID" etc.
> >
> > At present it allows me to add a new suburb etc into a form, but when the
> > form is closed it talks about "Item Not in list" but when I check the
> > Postcodes table it is actually there.
> > Thanks again
> >
> > "Roger Bell" wrote:
> >
> > > Have since got it to work.
> > > Your Patience and help has been much appreciated
> > > Thank You
> > >
> > > "Roger Bell" wrote:
> > >
> > > > Tried that Ken, but now get the error:
> > > > Could not find output table "Country_Birth"
> > > > Do I need a relationship between the Country_Birth Table and my Main Table?
> > > > and Autonumber field?
> > > > Thanks again
> > > >
> > > > "Ken Sheridan" wrote:
> > > >
>