Re: CLIENT_LOCALE values

Hi Everyone, I do want to apologize for spilling my frustration to the group. However, I offer none to anyone who uses obscene languages in public forum! There is a big difference between the tune of frustration and down right obscenity. Coming back to the problem, I tried all the suggestions and still no luck. My application normally runs as a Windows NT service, and this when the problem happens. This app can also run in a console window like a regular program, but when I do that the problem doesn't show anymore. I suspect there is a problem with the Intersolv ODBC Driver accessing the Windows NT registry, since CLIENT_LOCALE, DB_LOCALE and other variables are set in registry in Windows NT instead of in the environment. Anyone have any idea about this? Next week I will have to call up Informix, but I don't count on getting any good answers. I will probably be pushed back and forth between Informix and Intersolv. Big corporations run like bad government agencies. Thank you, and remember your mother may be reading as well. --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 > >