oracle application 11i


    Libraries

    Share
    avatar
    shrikantgarud
    Admin

    Posts : 109
    Join date : 2007-12-02
    Age : 31
    Location : Clover Infotech

    Libraries

    Post  shrikantgarud on Sun Jan 27, 2008 8:32 am

    Libraries contain reusable client–side code. They support these form
    coding standards by allowing the same code to be used by all forms to
    enforce specific validation, navigation and cosmetic behaviors and
    appearances.
    Libraries allow code to be written once and used by multiple forms.
    Additionally, because the executables attach at runtime, they facilitate
    development and maintenance without being invasive to a form.
    Every form requires several standard triggers and procedures to link
    the form with a library. Many of these triggers and procedures have a
    default behavior that a developer overrides for specific items or blocks.

    Application–Specific Libraries

    Each application is strongly encouraged to create its own libraries.
    Typically, each application creates a central library that governs
    behaviors of objects found throughout many of its forms. Additional
    libraries should be created for each major transaction form to facilitate
    the following:
    • Multiple developers can work on a single module, with some
    developers coding the actual form and others coding the
    supporting libraries.
    • Shipment and installation of patches to code is vastly simplified
    if the correction is isolated in a library. Libraries do not require
    any porting or translation.
    All libraries should reside in the $AU_TOP/resource directory (or its
    equivalent).

    Attaching Libraries

    Sometimes library attachments can be lost on platforms that have
    case–sensitive filenames. By Oracle Applications standards, library
    names must be in all uppercase letters (except for the file extension).
    However, for forms developed using Microsoft Windows, the library
    filename may be attached using mixed case letters, making the
    attachment invalid on case–sensitive platforms such as Unix. If you
    attach a library to a form in the Oracle Forms Developer on Microsoft
    Windows, you should avoid using the Browse mechanism to locate the
    file. Instead, type in just the filename, in uppercase only, with no file
    extension (for example, CUSTOM). Oracle Forms will then preserve
    the attachment exactly as you typed it. Note that your attachment
    should never include a directory path; your FORMS60_PATH should
    include the directory that holds all your libraries.

      Current date/time is Sat Sep 23, 2017 5:38 pm