|
| On Aug 31, 3:57 am, Erwin Moller
< Since_humans_read_this_I_am_spammed_too_
m...@spamyourself.com> wrote:
> Fad=A5 wrote:
>
>
>
>
> Hi,
>
> This MUST have to do with charactersets.
> I am not an expert on this, but what you need to find out is this:
> 1) Find out in which characterset MS SQL server is using to store data.
> (eg: latin1, UTF8, etc)
> You should be able to find this in via your management thingy in MS SQL
> Server.
>
> 2) Make sure your output uses the same characterset.
>
> Problem is: a certain bytevalue (or possibly multiple bytes in case of
> unicode) is just a value. What character it represents depend on the
> characterset you use.
>
> Things might be more complicated, but I would start there with your
> research.
> Hope this helps you going.
> Check in here again to see if somebody with better knowledge of
> characterencoding than me has some hints. :-)
>
> Good luck
>
> Regards,
> Erwin Moller
I checked! the database is using latin1 collation. so as you said i
should check what charset mssql uses when it binds to a database.
Thanks Erwin
|
|