Interface Libraries
This chapter includes the following sections:
Overview of Interface Libraries
The appropriate way to access the MicroKernel Engine from your Windows application is to link to a library that references the Btrieve Glue DLL when you compile. The Glue DLL is responsible for “glueing” your application to the Interface DLL. Like traditional glue (adhesive material), the Glue DLL is a thin layer between your application and the Interface DLL. The Glue DLL is responsible for successfully performing the following actions:
1 Loads the Interface DLL.
2 Binds to (that is, imports symbols from) the Interface DLL.
If the Glue DLL encounters a failure condition at any step, it issues an appropriate status code that your application can use to alert the user of the failure.
Table
27 shows the link libraries that your application can link with and the DLLs to load.
Table 27 MicroKernel Engine Programming Libraries
Operating System and Compiler1 | Glue DLL | Link Library |
Windows 32-bit (Microsoft Visual C++, Watcom, Embarcadero) | W3BTRV7.DLL | W3BTRV7.LIB |
Windows 64-bit | W64BTRV.DLL | W64BTRV.LIB |
1Compiler-specific libraries are in different subdirectories. To link Win32 applications, use the \Win32 directory if you use the Microsoft compiler; use the \Win32x directory if you use the Embarcadero or Watcom compiler.To link applications for UWP platforms such as Nano Server or Windows IoT Core, use the \winuwp directory. |
Linux and macOS
Linux and macOS have no glue components. The application directly links against the shared library that implements the interface. The MicroKernel Engine link library is libpsqlmif for both Linux 32-bit and Linux and macOS 64-bit applications.
Distributing PSQL Applications
If you plan to develop an application using a PSQL database engine, you need to be aware of the following requirements for distributing your applications:
Distribution Rules for PSQL
After you have developed an application with PSQL, you must be aware of the licensing agreement you have with Actian Corporation to distribute your product. If you have any questions regarding your distribution rights, please contact your sales representative.
Registering PSQL ActiveX Files
The following table includes the files required to run your application built with PSQL ActiveX interface:
Table 28 Redistributable Files
File | Location | Description |
ACBTR732.OCX | System directory | PSQL Data Source Control |
ACCTR732.OCX | System directory | PSQL Bound Controls |
PEDTCONV.DLL | System directory | Data conversion DLL |
PBTRVD32.DLL | System directory | Meta data handling DLL |
SBTRV32.DLL | System directory | IDS communication DLL |
SWCOMP32.DLL | System directory | Data compression DLL |
Once you have distributed PSQL ActiveX files and the required DLLs, you must register the ActiveX files so that they function correctly. There are two ways you can register these files:
•Many current installation utilities, such as InstallShield, can be modified to automatically register ActiveX controls during the installation process (for more information, see the documentation for your particular installation utility).
•Another way to register ActiveX controls is to install the redistributable file REGSVR32.EXE and run it during (or after) the installation process. This is a simple ActiveX registration utility that takes the name of the ActiveX to be registered as a command-line parameter (e.g., REGSVR32 C:\MyInstall\ACBTR732.OCX).
Installing PSQL with your Application
See Installation Toolkit Handbook for information on customizing the PSQL installation.