Archives of the TeradataForum

Message Posted: Fri, 24 Jun 2005 @ 22:10:02 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

From the question below, it is unclear about:

* File encoding (i.e. ANSI or UNICODE)

* The server character set for the CHAR() or VARCHAR() column (e.g. LATIN or UNICODE)

* The session character set used in MLoad and Queryman

* The version of Queryman as well as the ODBC --- 3.4 is different from other versions of ODBC

These are all important, especially when handling characters outside of 7-bit ASCII range.

Assuming that you have an ANSI data file, I would suggest to try the LATIN1252_0A session charset for both Mload and Queryman/ODBC so that DBS will convert your Western European characters between the session charset and the server charset correctly. If you rely on the default session charset (i.e. ASCII for the network client), only 7-bit ASCII characters will be converted/handled by DBS appropriately.

Tak T

	<Prev	Next>		<<First	<Prev	Next>	Last>>