Problem: I'm just getting started with the API, and looking at the examples, I see some "e" files, which are apparently embedded dynamic SQL things. How are these used? Solution: Embedded SQL files are written in C or another language, with extra SQL language statements "embedded" in the code. InterBase contains a development tool, called GPRE.EXE, which is a "preprocessor" to convert the .E file to a .C file. GPRE reads the embedded SQL statements and writes out the equivalent database operations in the form of InterBase API code. Typically you never have to look at the C code; you work exclusively in the .E files. When you are ready to compile, use GPRE to preprocess the .E file, then compile the output .C file using your favorite compiler. See the makefile in the examples directory. Embedded SQL isn't a visual programming tool, but it's a great way to write pretty abstract code and gain the benefits of programming directly with the InterBase API. ESQL even support SQL Roles! Embedded SQL is documented thoroughly in the InterBase Programmer's Guide. source: Bill Karwin
Last Modified: 26-OCT-00