Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Blastrix
Posting Yak Master
208 Posts |
 Posted - 2003-11-16 : 22:49:08
|
| I'm sure there's some people out there that have dealt with this issue before, but how do you deal with storing all of the different address types of the world? Coding for any one particular address is easy, such as the US, Street, City, State, Zip. But then a Japanese address comes along, or some other address that doesn't quite fit the mold. Should there be an individual table for each different type of address that can be presented(I really hope not). To me that would be an insane mess, but if not, then what are my options?Steve |
|
|
Blastrix
Posting Yak Master
208 Posts |
Posted - 2003-11-19 : 07:45:55
|
| Does anyone have any thoughts on this? Someone here must have dealt with this. |
 |
|
|
SamC
White Water Yakist
3467 Posts |
Posted - 2003-11-19 : 08:22:37
|
| It's a topic I've had to deal with in the past. It may be worth noting that Microsoft Outlook does a fair (not good or great) job of handling both US and international addresses. You might get some ideas if you examine how Outlook presents various addresses.Then there's international phone numbers. No way to parse that without a table of country codes and city codes. I'd be very interested in a set-based query that would take a phone number string, remove the special characters, parse it into country / city / phone, then maybe add the special characters for formatting. Brett did something with phone numbers earlier. |
|
|
|
Blastrix
Posting Yak Master
208 Posts |
Posted - 2003-11-19 : 18:24:32
|
| I followed one of the links in that thread to the MS GlobalDev site, and they pretty much say the same about addresses as they did about phone number...just go generic.Thanks,Steve |
|
|
|
|
|
|
|
|
International Address Storage?