With Version Control for Displays enabled, the DeltaV Operate files are listed in DeltaV Explorer. Therefore, you can export these files using DeltaV Explorer's import and export functions.
When Version Control for Displays is not enabled, the DeltaV Operate files are not listed in DeltaV Explorer. Therefore, you cannot export these files.
There are a couple of considerations when importing DeltaV Operate files.
- Version Control for Displays stores a copy of the graphic in the DeltaV database. This can make the database size large. Any full database exports from a system with Version Control for Displays enabled includes those graphics, making the FHX files large. Additionally, importing such an FHX file will increase the size of the new database, regardless of the state of Version Control for Displays.
- If you are importing a complete database from a DeltaV system that had VCAT for Displays enabled (at any point), the FHX file contains copies of those display files. When the FHX file is processed, the import log lists the graphics files as being imported.
- If you are importing from a DeltaV system that has VCAT for Displays enabled into a system does not have VCAT for Displays enabled, you will not see the DeltaV Operate files in DeltaV Explorer.
- If you are importing from a DeltaV system that has VCAT for Displays enabled into a system that also has VCAT for Displays enabled, and you have files of the same name but with different dates, you are prompted to overwrite existing files (yes or no).