locales and odbc
Posted in 1999
Topics: Installation, Setup & Upgrades, Connectivity: ODBC / JDBC / .NET, Connectivity: ESQL/C, 4GL & Embedded SQL, Internationalization & Character Sets
Hi,
Can anyone react to the following :
Situation :
SE database on SCO 5 / informix 7.22
GLS database necessary with for example
DB_LOCALE=fr_FR.ISO8859-1to be able to execute sql statements from within ESQL/C and
isql containing speciale characters (', ' ,etc.) on the Unix side.
Connection over the network from PC with Connect installed.
(Informix Client Software development kit 2.0)
Informix SetNet32 configured.
With
CLIENT_LOCALE=fr_FR.819we are able to access the information on the unix side via Borland
SQL-explorer and C++ Builder programs.
This works ok (so far) with the native driver from Borland SQL-links
and with both the ODBC drivers
- informix 2.80 32 bit
- Intersolv 3.20 32 bit Informix 9
We can also access en_us.819 databases with these settings.
But :
We fail to make the connection from within EXCEL.
It is only possible with databases that are created without DB_LOCALE
variable
(so the locale in the database systables en_us.819 does work ok)
We notice that
- the informix 2.80 driver asks to few questions when configuring from
within
the wizard upon getting external data. The Translation options do not show
and
the locale settings do not show. When trying to connect, we get the error
that to few
configuration information is given.
-When using the intersolv driver, we get the remark : Syntax not allowed.
Mind, this only occurs when trying to connect to a database with
non-standard locale
settings ( other than en_us.819) and with CLIENT_LOCALE set accordingly on
the
PC side.
Once more : the connection is ok from within Borland tools.
It seems the Borland tools use the SYSTEM.dsn
where EXCEL uses the FILE-dsn.
When you try to configure the File.dsn from within the ODBC applet on the
configuration
panel, you also get to few questions.
The same driver used in SYSTEM-dsn there asks all the questions.
Furthermore :
The configuration ONLY works (System DSN) when you use the DECIMAL form of
the code set name
So 819 is ok, ISO8859-1 not and neither is 0333.
PS
the regcopy.exe does not help in the Excel situation. cfr. Steven Smith,
Informix-FAQ
Any hints ?
Ralph Roef
Cerm benelux nv
ralph.roef@cerm.be
Hi, Upon further tests : It is possible to connect MS-Access via the Intersolv 3.10 driver. Initial connection is rather slow , but ok, he has to load the full systables. The 2.80 Informix driver seems to connect , but immediately says : "Syntax is not allowed in this database". We do get all the configuration questions , though, so the locales can be given. As opposed to Excel, we do get the User and System DSN tabs here. Hints anybody ? Ralph
Hi, for the record. Furher digging yields the following : Only File DSN's in Excel 97, unless Service Pack 2 is installed. The cd with service pack 1 and 2 can be ordered from Microsoft. This still leaves thee question why only the decimal form of the code sets can be used. Ralph.