Hello
As long as you use unicode datatypes (nvarchar, nchar, ntext), and
paramterized queries, you don't have to worry about queries. Of course the
length of the data can be language dependent, so you have to make the fields
big enough to hold information in all suported languages.
As for numbers and dates, they should never be stored in the database as
strings. Instead use bigint/int/smallint/tinyint/decimal/real datatypes for
numbers (depending on the type of number) and use datetime / smalldatetime
for dates. Then let .NET handle parsing dates and numbers and formatting
them for display depending on the culture used.
Best regards
Sherif
[quoted text, click to view] "faktujaa" <faktujaa@hotmail.com> wrote in message
news:A8A9967E-6050-4632-898F-51D2C1F454F5@microsoft.com...
> Hi Sherif,
> Im still confused. You mean to say that i don't have to do any coding to
make make my application international. Say for example, I have a chinese
user, he enters all his data in chinese language. I have made UI to display
chinese using CultureInfo and resource files. Now the chinese data has to be
stored in database. One thing for sure that it will occupy more/less space
than the english characters(I am not sure). So it is better to change the
database types to nchar/nvarchar/ntext as u say. But don't we have to store
the data in bytes to display it properly later. For example: Hello World in
chinese will be stored in database field Name as it is but when we see the
data appears to be junk, so will it display properly on the front end
without no query change. Don't we have to say SELECT ASCII(Name) from TABLE.
Another thing for all the above data types, can we use string to access
data?????? bcoz in C++, COM, we use to specify corresponding datatype for
datatype in SQL. This is all about string but how do we take care of
numbers. For example, numbers in Asian language-Hindi is having a different
format. Also dates???? I am dead by now. Please help. Thanx in advance.