Progress
DataServer for
Microsoft SQL Server
Guide
Compiling Progress Procedures
The COMPILE statement lets you compile Progress procedures and save the compilations to disk. This speeds up your application execution time since Progress does not have to recompile it every time you want to run a procedure.
To compile procedures that access an MSS data source, start up Progress and connect to the schema holder using the schema holder’s logical database name, then use the COMPILE statement. If you change the name of the schema holder after you compile a procedure, you must connect to the renamed schema holder and recompile the procedure. For more information, see the COMPILE Statement reference entry in the Progress Language Reference.
NOTE: You do not have to connect to the SQL Server™ database to compile a procedure. The schema holder contains all the information that the compiler requires.R-code
Progress generates r-code when it compiles a 4GL procedure. The compiled r-code is portable among machines. For example, r-code that you compile on a Sun machine can run on any other UNIX machine. R-code is also compatible across platforms. See the Progress Portability Guide for information on designing compatible user interfaces for applications.
R-code is not portable among windowing systems; that is, r-code compiled for a character application will not run under Windows and r-code compiled for Windows will not run under a character application.
R-code is also not portable among database management systems. Progress generates calls that are specific to a database. For example:
The size of r-code grows when you compile procedures against an MSS data source as compared to compiling against a Progress database. The r-code for a DataServer application contains as text portions of SQL statements that the DataServer passes to the data source.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |