Re: mssql versus odbc HELP

On Aug 31, 3:57 am, Erwin Moller
<Since_humans_read_this_I_am_spammed_too_m...@xxxxxxxxxxxxxxxx> wrote:
Fad¥ wrote:
Hello mates,

Something weird is happening or it's just the fact that I'm doing
something wrong.
When use mssql for db connectivity, and then i call mssql_fetch_array,
the values i get from the database will be retrieved with the special
charactes like "é" transformed to ",".
In the case of odbc that won't happen?!

Any Idea?

Thanks a lot!

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

.

Relevant Pages

  • Re: charset problem with =?ISO-8859-1?Q?=27=A4=27_=3F?=
    ... The effects on the existing data depend on the current characterset, new characterset and whether or not the data conforms to the characterset; if you've used the nasty hack to insert data that doesn't conform to the charset then that data will almost certainly be trashed. ... So if you've got an ¤ in the database represented by a Euro, and you change charset ... You might consider creating a new database as a possible alternative to changing the current one, then use exp/imp and verify/fix the new database, then redirect the clients to the new database, then finally delete the old one if it's no longer needed. ...
    (comp.databases.oracle.server)
  • Re: what characterset to use?
    ... would never corrupt your data in a WE8MSWIN1252 database character set ... WE8MSWIN1252 is a *single* byte characterset. ... If your database has been set up correctly (which is ...
    (comp.databases.oracle.server)
  • Re: WE8ISO8859P1 convert to AL32UTF8 unicode character set question
    ... AL32UTF8 database. ... If the varchar2 can be converted to target characterset and can be ... It can cause unpredictable conversion. ... UTF-16 encoded, Data retrieved from or inserted into the database must ...
    (comp.databases.oracle.server)
  • Re: what characterset to use?
    ... So if you have a database on Unix, as Unix doesn't support MSWIN1252, ... the database characterset should WE8ISO8859P15. ... So if he states it 'SOUNDS LIKE' Oracle recommends setting everything ...
    (comp.databases.oracle.server)
  • Re: Produce XML with russian text
    ... a 3.23.x MySQL version. ... To get back the data in Memo's and save them in the database there are no problems, only when I want to save them in an external file in an xml with utf-8 encoding. ... retrieving and displaying the data in a Russian characterset. ... As I see all the russian characters are saved in widestring russian characterset in the mysql database, because every of them looks excatly as before save in the Delphi Components like memo. ...
    (borland.public.delphi.thirdpartytools.general)