Overview

In 4D, you have the possibility of moving objects between two applications in the Design environment. You can thus recopy the tables, forms, methods, etc. that you have created in one database into another. This can greatly facilitate and accelerate database development. 

Moving objects is not limited to individual objects, it can also concern any objects that are referenced by the object, i.e. its dependent objects. You can thus move entire functionalities. For example, if you have created a custom query dialog box, you can move the form used for the dialog box as well as all the methods, pictures and other objects it uses. You can copy the form into another database or into a library grouping the functionalities currently used in your databases.
Certain objects are also inseparable: they are obligatorily moved along with their “parent” objects. The list of inseparable objects is provided below.

Objects can be moved from the Tool box, the Explorer and the Form editor. Moreover, it is possible to carry out a move from the results window of a Find in design search (see the Results window section).

For structural consistency, copying certain objects will lead to the copy of any objects that are inseparable from them. For example, copying a form will lead to the copy of any form method and/or object methods that are attached to it. These inseparable objects cannot be moved directly on their own. 

Here is a list of movable objects along with their inseparable objects:

Objects can be moved either using standard drag and drop or by copy/paste. 

To move objects between two databases using drag and drop, you must duplicate your 4D application. 

In the case of inter-database moving, moved objects can be pasted or dropped into the same environment as that of their departure (Tool box, Explorer, etc.) or into other areas of the application. 4D will carry out the appropriate action according to the context, whenever possible. For example, it is possible to drop a form onto the Method editor window; in this case, the name of the form is inserted into the method. 

During a move, if an object of the same type and with the same name already exists in the destination database, by default the existing object will be replaced by the moved object. The Moving dialog box will be displayed in this case; it indicates the objects that will be replaced and lets you modify this action. 

The following mechanisms should be noted:

• Views and level: Form objects that are moved keep the same location properties as in the editor, in particular their position in the views or in the different levels of the form.
• Inherited forms: Inherited forms are not moved with the source forms, however their reference is kept. Moreover, inherited forms are considered as dependent objects and it is possible to use another (existing) form as inherited form when the move is carried out (see the following section).
• Access rights: Forms and project methods that are moved do not keep their original access rights. They are automatically given the default value (“All groups”).
• Folders: When you move a folder from the Home page of the Explorer, the operation includes the folder and all of its contents (tables, forms and project methods), which can represent a considerable volume of data. During this type of move, a warning dialog box will appear to indicate this functioning.

Note: It is not possible to drag objects from the Trash page of the Explorer.

• A form (table or project) can refer to various other objects like lists, pictures, etc.: these objects are called dependent objects. In certain cases, you may need to move all the dependent objects whereas in others, you may only want to move some or even none of these objects. 4D lets you control the moving of dependent form objects via moving Preferences as well as a specific Moving dialog box.
  Moving Preferences specify the principles to be applied for moving dependent objects. You can choose various default options for each type of object. For more information, refer to WEB SET HOME PAGE.
• Beginning with 4D v13, tables referenced in methods are now moved by default along with the methods. You can disable this by holding down the Shift key when you drag methods from the results window or Explorer.