Hi!

I had similar problem recently, and I solved it by setting proper collation for field.
Open table for designing in Enterprise Manager, select field and look for "Collation" property of field at the bottom of designer window. I think, if you change it for Korean field, for example, it would not spoil data for other fields.

>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