RE: Problems with CLI 2.80 and Windows NT 4.0 ODBC

Lutz, We are encountering similar problems when trying to access an SAP database (German locale) through an ODBC connection. Everything worked fine with Informix-CLI 2.5. However, the connection from a Windows NT 4.0 workstation fails with the following error message when I use CLI 2.8 or the Intersolv 3.01 Driver: [Informix][Odbc Informix Driver]Database locale Information mismatch. I installed the new CONNECT software in the directory as the older Informix-CLI 2.5. It no longer works and generates the same error message. I have reported the problem to Informix Technical Support, but have not received a response yet. Rick Rick Bernstein Phone: (619) 458-7048 Principal Database Administrator FAX: (619) 458-7640 Alaris Medical Systems E-mail: rbernste@alarismed.com San Diego, CA 92121 -----Original Message----- From: Lutz Marten [mailto:Lutz.Marten@mail.uni-wuerzburg.de] Sent: Monday, August 17, 1998 01:03 To: informix-list@iiug.org Subject: Problems with CLI 2.80 and Windows NT 4.0 ODBC Hello, I have a problem using the newly released CLI 2.80 for Windows NT. The parameters that worked with CLI 2.30 on server and client are CLIENT_LOCALE=de_De.8859-1, DB_LOCALE=de_de.8859-1@bund .But after installing CLI 2.80 and using the same ODBC source (or create a new one) Microsoft Acces always displays an error: [Informix][Odbc Informix Driver]Database locale Information mismatch. (#-23197)[Microoft][ODBC Driver manager] Drivr's SQLSetConnectAttr Failed (#0) I tried both ways to set CLIENT_LOCALE and DB_LOCALE, by setnet32 and directly in the ODBC source creation dialog. I found out that if I leave the fields CLIENT_LOCALE and DB_LOCALE blank in the ODBC source setup dialog, the driver always fill in en_us.1252 , so that it seems unpossible to try to use the new driver without an entry for the two parameters in the ODBC source. Can anyone help me how to fix this error ? The main reason for using CLI 2.80 is, that the save-password feature should work and the fix of the problems with the access to NVCHARACTER from Windows NT. Thanks and regards, Lutz -- Lutz.Marten@mail.uni-wuerzburg.de , University Wuerzburg, Germany