hi Uwe,
I am not a neird on Windows platforms, therefore my stupid questions:
0) statement: the value you use is in line with the sysdbslocale value!
1) beyond your display issue from ODBC setting, does you application work as you expect? Does the issue appear only when setting the value? What happens when you click on 'Apply and test connexion' ?
2) Is the DB Server Unix or Windows? If Unix, this might explain some difference between CLIENT_LOCALE and DB_LOCALE which sometimes have different names for the same character sets.
3) Did you check whether you ( or someone else ) did not set a Windows environment variable, in the "environment variables" configuration page, called CLIENT_LOCALE OR DB_LOCALE, in addition to info in setnet32 and ODBC driver?
4) you seem to have a patched version, which might explain some strange behaviour with ODBC... ( well, just to write something, probability is weak...)
Do you have the latest 3.50 CSDK ?
If all this doesn't work, I'm gonna have to ring my friend domus ...
Hope this helps
Eric