Ok, I am quite prepared to start a flame war over this silliness.

"knowing the correct database to build should be a snap"

Go back to school JJ B, then get a job and do some "real" work for a few years before starting into the group of -hugely- experienced people who this forum represents. Or for that matter, before starting into the uneducated neophytes of the DP, IT, IM, ITC... industry of whom I'm a representative.

There are a number of threads on this site related to idiocy, perhaps the moderator could move this thread there, then if s/he wishes, ban me for my deliberately inflammatory statements.

If I'm still live here after this post, then, JJ B, try building a group of tables that store international physical and postal addresses, with a perorg relationship (where the person and organisation are included), and each person can be represented in multiple organisations, with temporal integrity, and each organisation has multiple international postal or physical addresses, with temporal integrity, and each person has multiple international postal or physical addresses, with temporal integrity, in 5-normal then come back to this forum and demonstrate that "the correct database to build should be a snap".

Else, oh I don't know, go and drink a quart of bourbon and hope the problems go away.

But please please please, DO NOT implement "the correct database" for any commercial organisation, regardless of how much they want to pay you, on the the basis of the erroneous "knowledge" that you present here.