No, the collation setting is not used for the conversion between Unicode and
an 8 bits code page and vice versa. Collation orders are only used on the
SQL-Server for comparing the equality or the sort order between two strings
and are never used for conversion between a particular code page and
Unicode.
My guess would be that the code page setting for Window on the served would
be used; however, at today's price for hard drives, you shouldn't use
varchar anymore on the SQL-Server. If you are concerned with non-latin (8
bits) caracters, the use of varchar will be a continuous moving target.
See the following articles for more information:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/sql_dataencoding.asp
http://support.microsoft.com/default.aspx?scid=kb;en-us;322112 --
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
[quoted text, click to view] "Glenn" <glenn.potter@agfa.com> wrote in message
news:kU2Me.134868$wr.106304@clgrps12...
> After executing a select query the data provider returns the value in a
> varchar field to a .NET string, how does it determine the encoding
> conversion to perform? My guess is that it's determined by the collation
> setting on the column, but I'm not sure? For example, if the collation is
> SQL_Latin1_General_CP1_CI_AS, the Provider converts from code page 1252 to
> Unicode.
> Does anyone know for sure the strategy applied here?
>
>