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

Moving and Copying Objects in the Object Navigator

You can use the following commands to move and copy objects within modules in the Object Navigator:

Restrictions on Copy/Move Destinations

The following restrictions apply when moving and copying objects in the Object Navigator:

How Object Ownership Affects Copy/Move Operations

When you move or copy an object, you also move or copy any objects owned by that object. For example, copying a block also copies the triggers attached to that block, the items owned by that block, and the triggers attached to those items.

It is important to distinguish between object ownership and the simple associations that can exist between objects. For example, canvases are displayed in windows, and each canvas is assigned to a specific window at design time. However, the window does not own the canvas. Both objects are owned by the form. The relationship between the window and the canvas is simply an association that you define by setting the canvas's Window property.

When you move or copy an object, only objects owned by that object are moved or copied. The ownership rules for objects in form modules can be stated simply as follows: Items and relations belong to blocks. Triggers can belong to items, blocks, or forms. All other objects belong to forms.

The ownership rules for menu modules are even simpler: Menu items belong to menus. Menus belong to menu modules. All other objects belong to menu modules.

PL/SQL library modules contain only subprograms and packages, all of which belong to the library module.