A script-enabled browser is required for this page to function properly.

About Compiling Libraries

Unlike form and menu modules, library modules do not have to be compiled explicitly to create a separate runfile. The .PLL library file that you work with in Oracle Forms includes both the source code required at design-time and the compiled executable code required at runtime. Using the .PLL version of the library is required when you want to use the Debugger to view the source code within compiled program units.

When a library is attached to a form, menu, or to another library in Oracle Forms, the .PLL version of the library is also attached. To run the application from Oracle Forms, you need only make sure that the subprograms and packages in the library have been compiled. (See Compiling all units in a module.)

When you are ready to deploy your application, you can compile a .PLX library file from the .PLL library file. The .PLX file does not include the source code component that is part of the .PLL file. You can compile a .PLX file from Oracle Forms or from the command line.

When you attach a library to a module in Oracle Forms, you attach the .PLL version of the library. At runtime, Oracle Forms looks for a .PLX file by that name in the default search paths. If no .PLX file is present, Oracle Forms looks for the .PLL file by that name.

You'll need to compile rp2rro.pll into rp2rro.plx if your Form depends on this library. rp2rro.pll can be found in ORACLE_HOME/forms/rp2rro.pll. The resulting plx should be in your FORMS_PATH.


Compiling a module to create an executable runfile

About compiling modules

Compiling a .PLL library

Attaching a Library to a Module