Databases Reference
In-Depth Information
EXCEPTION WHEN OTHERS THEN
NULL; -- logging can be done here!
END;
If the intersection item
P250_shuttle
is called and the driving table ID is stored in
P250_id
, the call to this procedure could look as follows:
set_selectlist ( p_list => :P250_shuttle
, p_intersection_table => 'dep_pages'
, p_lookup_fk_name => 'pag_id'
, p_master_fk_name => 'dep_id'
, p_master_fk_value => :P250_ID );
Simple report
If we have only one simple read-only table or query for a page, we can use a SQL
report or an interactive report. With the latter, the user has a lot of possibilities,
including the presentation and iltering of the data.
Other pages
There are always certain pages that don't fall in the aforementioned categories, with
special functionality—for example, parameter sections or charts with management
information. These pages must be built up with separate regions and after that those
must be attached together. Another example is a wizard for the end user that can be
used to accomplish rather complex input tasks with validations between the sub-
screens.
Summary
With every new version of APEX, new features and capabilities are being added
to the tool and it's constantly evolving. It's almost impossible to describe all the
possibilities of APEX in this chapter, but with the information in this chapter you
will be able to kick start and structure your development.
In this chapter, we got an overview of the installation and preparation tasks before
actually building the application. We discussed User Interface Defaults and the
application structure. We saw techniques to transform the data model into initial
screen designs. We also discussed a lot of best practices and guidelines during the
building phase.
In the next chapter, we will be using some advanced database features to enhance
our application.
