Moving an instance
You can move one or more selected instances to another existing project while keeping all their links (references, keywords, and instance calls for example). The generation parameters of these instances are automatically modified. If a generated file is nested under an instance, it is automatically displayed under the instance in the target project.
Procedure
- Close the design editors of the instances that you want to move to prevent any inconsistencies. Moreover, if its editor is being edited, an instance cannot be moved.
- Right-click one or more instances in the Design Explorer view and select .
- In the wizard that opens, enter a target project and click OK.
Results
Note: If you migrate Pacbase
applications and if a Library is split into various projects, the target project might not contain
generation options. Then, the generation parameters point to the generation parameters of the
project that is the parent of the target project in the ascending hierarchy of the design build
path.
You must verify that the links are resolved after the move. Some links might have become unresolved as the result of the move.
If a generated file was nested under an instance
in the initial project, it is also displayed under the instance in the target project. However, it
is desynchronized (
) because the instance design changed when the generation parameters were automatically
updated. The project that is displayed on the line of the generated file in the Design
Explorer view corresponds to the initial project. When you generate again, the following
two cases are possible, according to the COBOL target in the
Definition tab of the instance:

- If it has kept its default value, the file is generated again in the same project as the moved design.
- If it contains another value than the default value, the file is generated again in the specified COBOL target.