To manipulate images in image items.

A master detail relationship is an association between two base table blocks- a master block and a detail block. The relationship between the blocks reflects a primary key to foreign key relationship between the tables on which the blocks are based.

Any event that makes a different record in the master block the current record is a coordination causing event.

There are two phases of block coordination: the clear phase and the population phase. During, the clear phase, Oracle Forms navigates internally to the detail block and flushes the obsolete detail records. During the population phase, Oracle Forms issues a SELECT statement to repopulate the detail block with detail records associated with the new master record. These operations are accomplished through...

There are three most common types of complex master-detail relationships:master with dependent detailsmaster with independent detailsdetail with two masters

Cascade Isolate Non-isolate

Master Deletes Property Resulting Triggers ---------------------------------------------------- Non-Isolated(the default) On-Check-Delete-Master On-Clear-Details On-Populate-Details

Master Deletes Property Resulting Triggers --------------------------------------------------- Cascading On-Clear-Details On-Populate-Details Pre-delete

The coordination properties are Deferred Auto-Query These Properties determine when the population phase of blockcoordination should occur.

A user named editor has the same text editing functionality as the default editor, but, because it is a named object, you can specify editor attributes such as windows display size, position, and title.

A user named editor can be displayed programmatically with the built in procedure SHOW-EDITOR, EDIT_TETITEM independent of any particular text item.

Show editor is the generic built-in which accepts any editor name and takes some input string and returns modified output string. Whereas the edit_textitem built-in needs the input focus to be in the text item before the built-in is executed.

Record Group.

When LOV for Validation is set to True, Oracle Forms compares the current value of the text item to the values in the first column displayed in the LOV.Whenever the validation event occurs. If the value in the text item matches one of the values in the first column of the LOV, validation succeeds, the LOV is not displayed, and processing continues normally. If the value in the text item does not match...

Show_lov List_values

set_item_propertyget_item_property(by setting the LOV_NAME property)

Get_lov_property set_lov_property

A record group is an internal Oracle Forms that structure that has a column/row framework similar to a database table. However, unlike database tables, record groups are separate objects that belong to the form module which they are defined.

A record group can have an unlimited number of columns of type CHAR, LONG, NUMBER, or DATE provided that the total number of column does not exceed 64K.

A query record group is a record group that has an associated SELECT statement. The columns in a query record group derive their default names, data types, had lengths from the database columns referenced in the SELECT statement. The records in query record group are the rows retrieved by the query associated with that record group.What is a Non Query Record Group?