The usual practice for developing applications that use functions from DLLs is to link the application against an import library, which contains the required function definitions.
This section describes an alternative to using an import library for developing Windows-based embedded SQL applications. DBLIB can be loaded dynamically, without having to link against the import library, using the esqldll.c module in the SDK\C subdirectory of your installation directory.
A similar technique could be used to dynamically load DBLIB on Unix platforms.
Load the DBLIB interface DLL dynamicallyYour program must call db_init_dll to load the DLL, and must call db_fini_dll to free the DLL. The db_init_dll call must be before any function in the database interface, and no function in the interface can be called after db_fini_dll.
You must still call the db_init and db_fini library functions.
You must include the esqldll.h header file before the EXEC SQL INCLUDE SQLCA statement or include sqlca.h in your embedded SQL program. The esqldll.h header file includes sqlca.h.
A SQL OS macro must be defined. The header file sqlos.h, which is included by sqlca.h, attempts to determine the appropriate macro and define it. However, certain combinations of platforms and compilers may cause this to fail. In this case, you must add a #define to the top of this file, or make the definition using a compiler option. The macro that must be defined for Windows is shown below.
| Macro | Platforms |
|---|---|
| _SQL_OS_WINDOWS | All Windows operating systems |
Compile esqldll.c.
Instead of linking against the import library, link the object module esqldll.obj with your embedded SQL application objects.
Sample |
Discuss this page in DocCommentXchange.
|
Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1 |