Linking the ESQL Executable
After successfully compiling your source files, you have a corresponding number of object files. Link your object files with Progress object files to produce an ESQL executable. The Progress objects you link with depend on the type of executable you are building:
Except for Windows small clients, you can link your executable using a link script that the
PROBUILD
utility generates. For Windows small clients, you use your own link script. For more information, see Building and Running ESQL Applications." For information on thePROBUILD
utility, see the Progress Client Deployment Guide.Functional Layers of an ESQL Executable
Figure 1–7 shows the functional layers that constitute a large client and small client executable.
Figure 1–7: Large Client with Compiler-functional Layers
![]()
Figure 1–7 demonstrates an ESQL executable that is built from your ESQL application code and Progress code (provided in object form). The Progress code consists of the following functional layers:
- ESQL-LIB interface — Progress/ESQL support library. This is part of any small or large client executable.
- SQL Compiler — Code that compiles your SQL statements, in some cases, generating r-code files for those SQL statements. If a statement is compiled into r-code, it is not recompiled unless you delete its r-code file. This is part of any large client executable and the OID.
- Run-time manager — Code that runs compiled SQL statements (r-code files). This is part of any large client executable and the OID.
- Database manager — Code that handles all database access and much of the processing involved in query resolution. This is part of any large client executable and the OID.
NOTE: Communications layers (not shown) are also available for all ESQL executables and the OID.For more information on linking ESQL source files, see Building and Running ESQL Applications."
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |