Problem: Client Library vs. DB Library (System 10)
A lot of things can be covered on this. What it boilsdo
wn to is that IDAPI in
its current incarnationdo
es not support System 10 Client Library API (CTLIB.DLL).
The only way to connect to a System 10 server is to use the DBLibrary API
(W3DBLIB.DLL). Having said that, consider the alternative.
IDAPI can connect to many different file formats and database back-end systems/SQL
servers via ODBC drivers. That means systems that are not normally tested or
supported. Here then
is a way to get to
System 10 and CTLIB API. To make it happen, you'll need the latest ODBC drivers
from a vendor that has developed a driver (MS, Intersolv, etc.) for System 10 and
the Client Library API. Some things you may run into setting up these drivers
through the ODBC Admin utility are listed below:
Problem: Setting up the DSN (DataSource Name) for System 10 gives an error message
claiming that there is not enough memory to run the setup routines for this driver.
Solution: In almost all instances of this error, it is because the DLLs that
support CTLIBdo
not exist or cannot be found. Make sure the installation of the
client software has beendo
ne correctly. Often times, the user just needs to
run the batch file WSYBSET.BAT. Here is a sample batch
file:
set PATH=C:/DOS;C:/WINDOWS;C:/QEODBC;C:/SQL10/BIN;C:/SQL10/DLL
set SYBASE=C:/SQL10
set DSQUERY=mercury
set INCLUDE=%INCLUDE%;C:/SQL10/INCLUDE
set LIB=%LIB%;C:/SQL10/LIB
set USER=pdox1
Here is a sample of the DLLs needed to connect to the NLM version of System 10:
WNLNOVSP.DLL 21,310 01-17-94 2:37p
SH20W16.DLL 37,376 08-24-93 1:00a
WCTLIB.DLL 303,271 02-18-94 3:19p
WCOMNLIB.DLL 229,555 03-01-94 3:48p
WBLKLIB.DLL 55,953 01-18-94 3:31a
WINTLLIB.DLL 35,725 01-17-94 9:47p
WTCLLIB.DLL 113,599 03-08-94 10:32a
WCSLIB.DLL 43,047 02-18-94 10:20a
SH20MON.EXE 7,168 02-03-95 4:14p
Here is a sample of the network DLLs needed in addition to the latter:
NWIPXSPX.DLL 35,308 05-24-94 4:00p
NWNETAPI.DLL 106,047 05-24-94 4:00p
