Re: NLS with Online workgroup server

>Now, i tried to do the same on the NT-Server using the Command Line >Utilities and setting LANG,DBLANG,DB_LOCALE and so on to de_DE.ISO8859-1, >but all database i create (dbimport oder manually in dbaccess) are still >set to en_US.819 ?! How dis you set the environment ? Now Win32 Informix uses the registry to store them, and the command-line environment is not used for all variables (there are priorities). Use Informix SetNet32 tool to set the client environment within the registry under NT and W95. All information about Informix in the registry are now stored under the following keys: HKEY_LOCAL_MACHINE\\Software\\Informix: global installation settings HKEY_CURRENT_USER\\Software\\Informix: user-level profile, which is one of: HKEY_USERS\\*\\Software\\Informix New users may inherit automatically from a default user profile by assigning the .default user instead of the current user. You may also find it useful to use RegEdit, and export HKEY_CURRENT_USER\\SoftWare\\Informix into a file (say hkcu_ifx.reg), so that other users will be able to double-click on that file to load their default preferences from a common user environment. Then the only thing to do for them is just to change the password options with SetNet32. The same could apply if you want to copy a configuration from one Win32 client host to another without having to launch the complete Install program. Just export (on an installed and working machine) with RegEdit HKEY_LOCAL_MACHINE\\Software\\Informix into a file (named hklm_ifx.reg for example). You can then selectively remove the locale files you don't need and which take much space in the gls directory. They can be safely removed from client hosts. For Win32 clients, the only locale you absolutely need uses the ISO8859-1 locale (859), and your default Windows language. Keep also the English version because not all tools are localized in all languages. Keep the PC850 charset for command-line tools. The PC437 will normally be unused, unless your command-line tools are being run from a command-line using the (now obsolete) 437 codepage (type CHCP to know which codepage your command-line interpret uses). The Roman8 will be useful if your Informix server is being run under HPUX with databases created in its default HP-Roman8 character set. But you should better set your HPUX server with the ISO8859-1 environment, so that it will more safely manage Win32 command-line tools (PC850) and GUI applications (ISO8859-1). And unless you need Chinese, Korean, Japanese, Greek, or Cyrilic languages, you won't need to set your server to the Unicode charset, because it uses much space for CHAR(n), VARCHAR(n) and TEXT data. As an alternative, you may use the extended Unicode UTF8 encoding but this creates other SQL problems due to varying length encoding of characters. Then distribute a copy of your installed Informix directory along with the two .reg files, and make sure these files are copied on the same directory tree. This is of great help when installing multiple machines from the network, because all you have to do is copy the directory tree on the new client machine, and launch the two .reg files on that machine. Then when this new W95 or NT machine accepts a new user, all that has to be done is just launching the hkcu_ifx.reg file to store the default user profile in the registry. Note: the Informix 859 codepage is only a 7-bit codepage, which despite its full name does not support the complete ISO8859-1 charset, but only its compatible ASCII character subset. So do not specify: "en_US.ISO8859-1", but use instead the: "en_US.ISO8859-1@dict" with the @dict modifier to use the complete character set (see your GLS documentation). Failing to do so will produce undesirable exceptions from a NT server due to invalid character conversions if ever an extended character is found in a string.