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

Understanding the User's Perception of Information

Window layouts should be based on the logical relation of data, not the physical database tables. For example, in the Sales and Marketing product, a user perceives an 'Account' as the specific data of the Account, as well as the 'Contacts' and 'Executives' of that account. These three entities are stored in separate physical tables, but by placing them all in a single set of windows, the user continues to perceive them as one logical object.

Note: Oracle Forms will ask the user to save changes when a new master record is selected and changes are pending in the detail block. This breaks the unity of both a logical object and a transaction by exposing the block- and record-level properties of each, but was judged to be infeasible to circumvent.