Hi Sergey,

Yes, I'm using nchar or nvarchar for the field data types. When I go to the translation service and get my english to korean translation, I properly see the sympbols in the browser, then when I cut and past into SQL Server I get ASCII boxes. Maybe there is something else I am missing, fonts ??? , keyboard drivers ???, ASCII extended codes ???. As a matter of fact if I cut and past the symbols in to wordpad or anything else I get the ASCII characters.

This is my first foray in to the languages with symbols and I'm not sure where to start...

Thanks,
Jace

>Jace,
>
>Are you using Unicode data types nchar, nvarchar, and ntext? I think it's only way to satisfy your requirements.
>
>>I have one table in my new program in SQL 2000 that needs to have data from almost every different language. Each row will be it's own language. Example:
>

>
>>Lang_Id     Lang_Field_Id     Lang_Field_Value
>>----------------------------------------------
>>EN          First_Name        xxx
>>ES          First_Name        xxx
>>DE          First_Name        xxx
>

>>Everything is working fine through the variations of Spanish, French, Italian and German, but when I get to Korean, Japanese, Chinese I cannot save the characters in the database, it is giving me "whacked out" (how's that for a technical term) ASCII box characters. I figure I need to do something with the collation, but am worried that will mess up the data that is already in there and working fine for my users.
>>
>>Just wondering if there is anybody out there who has any experience with Korean, Japanese or Chinese language in regards to SQL.
>>
>>TIA !!!
>>
>>Jace