Re: [Firebird-odbc-devel] Charset and dialect in DSN

[Kjell R. <kje...@ad...>]

Jorge,

 From the SQL Server ODBC driver help:

-------------------------------
Perform translation for character data check box

When selected, the SQL Server ODBC driver converts ANSI strings sent 
between the client computer and SQL Server by using Unicode. The SQL 
Server ODBC driver sometimes converts between the SQL Server code page 
and Unicode on the client computer. This requires that the code page 
used by SQL Server be one of the code pages available on the client 
computer.

When cleared, no translation of extended characters in ANSI character 
strings is done when they are sent between the client application and 
the server. If the client computer is using an ANSI code page (ACP) 
different from the SQL Server code page, extended characters in ANSI 
character strings may be misinterpreted. If the client computer is using 
the same code page for its ACP that SQL Server is using, the extended 
characters are interpreted correctly.
-------------------------------

I suppose either option might work in most cases, but doesn't it sound 
like the usual "I don't really know what this MS software is doing, but 
I hope it works"? Firebird gives you full control. Is that bad?

Kjell

Jorge Andres Brugger wrote:

> I have SQL Server and MySQL ODBC DSN here, and none of them asks for 
> charsets (being dialect IB/FB exclusive).
-- 
--------------------------------------
Kjell Rilbe
Adressmarknaden AM AB
E-post: kje...@ad...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64