![]() ![]() |
|
Database DriversThe jBASE design provides for database independence by allowing end users to code additional database drivers thus enabling a infinite number of database types to be used by the same application. In addition jBASE provides an example of how to interface to the jBASE jEDI drivers.
EXAMPLE OF APPLICATION INTERFACE INTO JBASE JEDI DRIVERS.Copy the "jediCExample.c" program from the "src" subdirectory in the jBASE release directory and compile. Unix Windows Execute CExample as CExample -Options InputFile OutputFile
EXAMPLE OF JBASE JEDI DRIVER.Copy the "jediDExample.c" program from the "src" subdirectory in the jBASE release directory and compile. Unix Windows Create jBASE File Pointer Create standard directory with ".d" suffix Edit jBASE File Pointer List directory EXAMPLE.d
EXAMPLE JBASE JEDI SUBROUTINE DRIVERCopy the "GEN_SUB.b" program from the "src" subdirectory in the
jBASE release directory and compile. Create normal HASH files. Create jBASE File Pointer Edit jBASE File Pointer. List hash file.
EXAMPLE JBASE JEDI SUBROUTINE DRIVER FOR ORACLE ON WINDOWSCopy the "ORA_SUB.b" program and "sqlsubs.pc" from the "src" subdirectory in the jBASE release directory and pre compile with ORACLE compiler and then compile. Set library path to include Oracle libraries Set jBASE environment variables for ORACLE NT libraries and precompiler options. Copy jBASE jmv.exe to move.exe as required by jbc -Jqo options In SQL*PLUS create SQL table: Precompile sqlsubs error functions: Compile sqlsubs.c in to a .obj Precompile the ORA_SUB.b subroutine: Build a dynamic linked library contain your subroutine and error functions: Copy dll and def to your %HOME% "lib" subdirectory so it can be found by
jEDI: Create jBASE File Pointer Access SQL table via jEDI subroutine driver In SQL*PLUS check updates |