On Windows operating systems, the solidDB® ODBC libraries are provided as .DLL files.
The files are named socw32VV.dll and sacw32VV.dll (where VV indicates the version number) for the Unicode and ASCII versions, respectively. For example, the Unicode ODBC driver in version 4.1 is named socw3241.dll. To call the functions in one of these .DLL files, you must link to a solidDB® import library file. In Windows environments, the import library file is named solidimpodbcu.lib (Unicode) or solidimpodbca.lib (ASCII). This import library file contains the entry points to the corresponding solidDB® ODBC DLL (for example, socw3241.dll).
Note The library files have been produced with C++. Linkers by other development toolkit manufacturers might expect different library file formats. In such cases, the Import Library utility of the development toolkit should be used to build a library file that is compatible with your linker.
Instructions for usage of solidDB® client DLLs (solidDB® ODBC Driver files)
There are two alternatives to building application programs that use the solidDB® ODBC driver:
1 Using Microsoft ODBC Driver Manager.
Microsoft ODBC software needs to be installed on all client workstations and a Data Source must be defined using solidDB® ODBC Driver. If you use the Driver Manager, any application that can use the solidDB® ODBC driver works also with any other ODBC compliant engine.
2 Using solidDB® ODBC driver directly.
Connections are opened directly to a server process without using Microsoft ODBC Driver Manager. This can be useful in embedded deployments of the solidDB® server. However, the application can only use the functions provided by the solidDB® library (that is, solidDB® ODBC Driver); the application cannot use the ODBC functions that are implemented by the Microsoft ODBC Driver Manager or the Microsoft Cursor library.
The solidDB® server package provides some sample programs that can be used either with or without the Microsoft ODBC Driver Manager. The samples are in subdirectories of the samples directory in your solidDB® installation directory. Below are brief instructions on how to build and run the provided samples in both of the alternative ways:
Building the samples to use ODBC Driver Manager
1 Create a new application project.
2 Add the C-source file (for example, sqled.c or embed.c) to the project.
3 Make the header files visible to the compiler.
4 Define SS_WINDOWS for the compiler.
5 Compile and link.
6 Make sure that you have installed the solidDB® ODBC driver. Also, make sure that the connection string you intend to use is defined as the ODBC data source name.
7 Run to connect to a listening solidDB® server.
Building the samples to use solidDB® ODBC library directly.
The necessary changes to the ODBC Driver Manager configuration are listed below.
1 Add the solidDB® ODBC driver library file (solidimpodbcu.lib) to the project.
2 Remove ODBC Driver manager libraries ODBC*.LIB from the default library list.
3 Compile and link.
4 Now it is possible to connect to data sources bypassing ODBC Driver Manager. Make sure that the SQL API DLL socw32VV.dll (where VV indicates the version number) and the solidDB® communication DLLs are available. Data Sources can be defined in solid.ini or in the ODBC Administration Window.
5 Run the client to connect to a listening solidDB® server.