Hi,

I have setted in SQL server 2000 the column collation as
"Chinese_PRC_CI_AS" and the data type as "nvarchar".

When I try to update the value with ASP using the "update tblitem set
..." statement, I got the data stored in sql server like " & #24191;&
#1999;" which is not chinese simplified character. However, the
characters display correctly as chinese simplified character when
viewing through web interface.

Would anyone tells how to make the "actual" chinese simplified character
stored in database and will there any problem to store the data as " &
#24191;& #1999;" . Thanks for any help!!

--
Posted via http://dbforums.com

Since you did not specify how you actually tried to store the characters, it
is impossible to determine what is happening. One major point is whether
"&#24191" is actually being stored in the database (ie 7 chars) or your
client is only displaying it as such, and only 1 char was stored.

"&#24191" looks like an iso latin encoding of some Chinese character. A web
page using iso latin encoding may very well display the equivalent
simplified Chinese character. To avoid this, you should save your asp page
with utf-8 encoding and use the "<%@ CodePage=65001 %>" directive in the asp
page. Any strings in SQL statements should be prefaced with the N'....' so
that unicode is sent to SQL Server.


"ElaineB" <member32316@dbforums.com> wrote in message
news:3065051.1057118595@dbforums.com...
>
> Hi,
>
> I have setted in SQL server 2000 the column collation as
> "Chinese_PRC_CI_AS" and the data type as "nvarchar".
>
> When I try to update the value with ASP using the "update tblitem set
> .." statement, I got the data stored in sql server like " & #24191;&
> #1999;" which is not chinese simplified character. However, the
> characters display correctly as chinese simplified character when
> viewing through web interface.
>
> Would anyone tells how to make the "actual" chinese simplified character
> stored in database and will there any problem to store the data as " &
> #24191;& #1999;" . Thanks for any help!!
>
> --
> Posted via http://dbforums.com