The ODBC driver libraries must be linked with your client application program. You will then be able to call the functions that are defined in these libraries.
Static vs. dynamic Libraries
solidDB® provides both a static and a dynamic version of the ODBC driver library.
Static libraries are linked to your client application’s executable program at the time that you do a compile-and-link operation. Dynamic libraries are stored separately from your executable and are loaded into memory at the time your program executes.
The advantage of a static library is that your application is largely self-contained; if you distribute the application to your customers, those customers do not have to install a separate shared library in addition to installing your application.
The advantage of a dynamic library is that on many systems it requires less disk space (and, on some platforms, less memory space) if more than one client uses that library. For example, if you have two client applications that each link to a 5 MB static library, you will need not only 5 MB of disk space to store the staticlibrary, but also 10 MB of additional disk space to store both copies of the library that are linked into the application. However, if you link two client applications to a dynamic library, no additional copies of that library will be required; each application does not keep its own copy.
In Windows environments, solidDB® provides an import library in some cases. Each import library is associated with a corresponding dynamic link library. Your application will link to the import library. When the application is actually loaded and executed, the operating system will load the corresponding dynamic link library.