Solved: Problems with CLI 2.80 and Windows NT 4.0 ODBC

Hello, I got CLI 2.80 up und running. I found that the registry entry for the odbc source had been corrupt and one sqlnet parameter wasn't entered correctly. After fixing it using regedt32 it works. Many thanks again for all suggestions, regards, Lutz -- Lutz Marten, Lutz.Marten@mail.uni-wuerzburg.de, University Wuerzburg, Germany Lutz Marten wrote in message <35d7e3ea.0@uni-wuerzburg.de>... >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 > >