Re: CLIENT_LOCALE values

Sorry but this is not true... HKEY_CURRENT_USER\\Software\\Informix is accessed by INET (now called Informix-Connect), the layer below ODBC. But that`s probably not the Problem. Usually if you get this message, INFORMIXDIR is not set for this specific __USER__. On NT it is located in HKEY_CURRENT_USER\\Software\\Informix\\ENVIRONMENT (forget the normal process env - it`s not used anymore). BTW in most cases there is not need to set the CLIENT_LOCALE to any value unless you want to force the CLIENT_LOCALE to be different from the DB_LOCALE of the Server! Hope it helps "Michael Chen" <michaelc@hotmail.com> wrote: >I have determined that the Intersolv Informix ODBC Driver accesses >the NT registry at HKEY_CURRENT_USER\\Software\\Informix. Obviously, >Informix only consider the driver used in a user login session and >overlooked Windows NT services. > >I have posted a question in various NT groups on how to login as 'system' >and set these registry settings (run SetNet32.exe) to allow >a NT services to use this ODBC driver. > >Stay tuned > >--Michael > > >Michael Chen <michaelc@hotmail.com> wrote in article ><01bc71cc$36cad1e0$97c809c0@michaelc>... >> My ODBC application received error: -23101 Unable to load locale... >> The error message detail says I need to set CLIENT_LOCALE and >> DB_LOCALE. Fine! My problem is the evaluation does not come >> with the "Guide to GLS Functionalily", so I have no idea what >> are the accepted values! >> >> Would someone please just look it up and tell me what is the local >> value for US English? >> >> It is rediculus not to include such a important documentation in >> the evaluation! The SetNet32.exe help does not even give a hint >> about the possible value. If the writer can just include a example >> for English locale will save me all these trouble. >> >> Thank you >> >> --Michael >> >> Reply to: michaelc@hotmail.com >> >>