John,
I was interested in your comment about not having a lookup on city and state but rather have a ZIP lookup to help fetch the default city and state.
My question is whether you would follow the same strategy for postal codes structures that use a different strategy than the U.S. system? For example, in Canada, the postal code system does a much finer geographic breakdown than I understand is possible with the U.S. system.
A code consists of 6 characters in the format ANA NAN (giving Santa Claus the unique code H0H 0H0 :) ). The Post Office refers to the first three characters as the Forward Sortation Area (FSA). Small communities have only one FSA but larger cities may have several. I believe each FSA corresponds to one postal sorting/distribution centre.
It seems to me that it would be far less cumbersome to have a City lookup table with related State/Region and Country tables all connected by appropriate junction tables.
I may well be over-designing, as you say, but I would appreciate
hearing your insight.
Glenn
--- In MS_Access_Professionals@yahoogroups.com, John Viescas <JohnV@...> wrote:
>
> Bill-
>
> It's not normal to build a lookup on city and state. I have built a lookup on
> ZIP code that then fetches the default city and state for the selected ZIP. You
> may have overdesigned your database.
Tidak ada komentar:
Posting Komentar