database now needs to be global

[vapid2323]

Ok the Short of it is that I have created a database that was made for the US only so I have phone number masks and US address fields and zip codes.

Now my company is going global in a big way, we are talking about most major countries.

What tips can you guys give to prepare for this type of change? All I can think about right now is the phone numbers, zip codes etc but I am sure there is a lot I am missing.

EDIT: I just thought about it and this might not have been the best forum area to post this, if a mod wants to move it to the Genral area thats fine, sorry about that!

 

[DCrake]

From my experience of writing a multi national system the main thing to condiser are date formats, currency formats. Zip codes and phone no's are secondary, make sure you get this right first.

What I did was to have a system admin screen that when first installed the user set up their custom settings which were held in a table these were then adopted when the program was launched.

 

[vapid2323]

From my experience of writing a multi national system the main thing to condiser are date formats, currency formats. Zip codes and phone no's are secondary, make sure you get this right first.

What I did was to have a system admin screen that when first installed the user set up their custom settings which were held in a table these were then adopted when the program was launched.

Very good point, this is going to be intresting as this is my first, as you put it, multi national system.

I do have one thing going for me, I belive everyone that will be working with this tool should be in the US.

We will see where this heads but thank you for the feedback!