SQL and Chinese Characters
I have a classic ASP web application with MS SQL 2008 back end.
98% of my users use the regular keyboard, but there are a few that have a Chinese keyboard.
When they type in and save a field it shows weird characters after saving.
What needs to be done so that they save correctly ?
98% of my users use the regular keyboard, but there are a few that have a Chinese keyboard.
When they type in and save a field it shows weird characters after saving.
What needs to be done so that they save correctly ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Shaun Kline
One other item to be concerned with is that you are using nchar/nvarchar when saving data as these SQL data types can handle the double byte character set that the Chinese language uses. You may also need to adjust the language type for the columns in your SQL data tables as this can also cause issues when saving data. Start with Big Monty's suggestion first, though.
What's the collation set for the SQL Server instance and the database?
ASKER
it is: SQL_Latin1_General_CP1_CI_
Most users will enter information in English or Spanish, but we want to allow Chinese characters as well.
Is this possible without causing any issues to existing data and new data entered in Spanish or English ?
Most users will enter information in English or Spanish, but we want to allow Chinese characters as well.
Is this possible without causing any issues to existing data and new data entered in Spanish or English ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That is a whole lot of work, its basically having to duplicate the database. :#
any other ideas ?
any other ideas ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is not something feasible (migrating data, etc), for now it will remain the same way it is. Thanks for the help.
ASKER
I had to put this on hold but the two solutions may work. I won't implement until later this year, sorry.