Database Management
Reference Manual
Output Syntax
: Principles and Limitations
Principles and Limitations
Output listing can be used as a convenient medium for transferring data from one project to another or from one computer to another. Such lists may also be useful when a Project DB is upgraded to a newly released version of AVEVA E3D™. This chapter summaries the procedures which you might follow when carrying out such tasks.
The design to be transferred can include some of all of the following major categories of data:
•
The Project Configuration
•
Catalogue items, including Bolt Tables, Connection Compatibility Tables, etc.
•
Material Properties
•
Component Specifications
•
Three-dimensional Design layouts
•
User-Defined Attributes (UDAs)
•
Drawing Libraries and Drawings
To transfer a complete Project you would normally use the ADMIN Module. You would usually use output lists only for transferring specific parts of the Catalogue, Design, Drawing (PADD) or Dictionary (UDA) data.
Output cannot be used to transfer the Project Configuration; you must use ADMIN to output the configuration in a suitable format for transfer. This operation is included in this chapter simply to show where it fits into the overall operation.
Before any transfer takes place, you should consolidate the Project DB by removing all DB copies, leaving only the Master versions. You should also make sure that individual DBs have consistent and unique contents, thus avoiding, for example, an attempt to transfer two similar (but not identical) copies of the Catalogue.
When an Outfit listing is to be input to a Project DB, it is essential that all elements which are referred to in the list, but which are specified outside the list, have already been loaded into that DB. After the transfer of data to a new Project, the element reference numbers will almost certainly be different from the original and no reliance should be placed on their meaning. As a general rule, therefore, all items which are reference (such as Catalogue Components, Specification Components, etc.) should be named.
Note particularly that, if you use Outfit to transfer data from Design, Catalogue or Drawing (PADD) DBs which include User-defined Attributes (UDAs), the reloading process will fail if there are any UDSs for which definitions are not available in the target Project of if the definition in the target project is inconsistent with the definition in the source project. For this reason, UDA definitions held in the Dictionary DBs should be transferred first.
Note:
Cross-references between Branches and attached Nozzles may be lost during the transfer process. In this case, they must be reset in the newly created DB.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.
