View Full Version : Client Access Translation Parameter using VB & ADO
01-01-1995, 02:00 AM
Does anyone know of a parameter I can pass through ADO to tell Client Access to translate data to NT code page 1251 (Cyrillic) rather than 1252 (Latin)? I could use ODBC instead, which has such a parameter, but I want to ADO.
10-18-2000, 09:00 AM
Which OLE DB provider are you using, MSDASQL, IBMDA400, or something else? From what I can tell from my own exploration, VB and ADO communicate using BSTR's (Unicode). ADO and MSDASQL also communicate using BSTR's (Unicode). MSDASQL and the ODBC Driver Manager communicate using ANSI, so it is MSDASQL that converts the Unicode to the current ANSI code page. If the ANSI code page is 1252, any Cyrillic characters in the Unicode are lost in this conversion. Changing the ANSI code page to 1251 by setting the "default system locale" to one of the Cyrillic languages, or running on a Cyrillic Windows will correct this problem. IBMDA400, the OLE DB provider supplied with Client Access Express, will bypass this Unicode to ANSI conversion and go directly from Unicode to the EBCDIC CCSID of the database. If this CCSID is 1025 (Russian), you should be able to transfer Russian data even on an English NT.
Powered by vBulletin® Version 4.1.5 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.