Importing Reports to Target Applications
Note: In order for a target application to use report procedures, it must include repcomp.img and repopen.img.
1. Select the target database, if necessary, by entering a valid 'node_name::database_name' into the Database entry field.
2. If the Application list is not loaded or is out of date, click View/Refresh Applications. If the Applications option field displays "Load Applications" then selecting this option will also load the application list.
3. Select the target applications from the Applications option field.
4. If the Application Report List is not loaded or is out of date, click View/Refresh Reports, or if the Application Reports List displays "Load Reports" click on this row to load reports.
5. Click Reports/Import to Application or Reports/Write Install Script—only one of these options is available at a given time and is controlled by Reports/Options/Immediate.
If the selected report or any of its specified components (Reports/Options/Include) has not been saved during the current session you will be prompted to:
• Continue: Use a corresponding component on disk.
• Cancel Install: Abort attempt to import the procedure.
• Save Now: Export the required components and continue. If some requested component cannot be saved you will be allowed to cancel the installation.
Otherwise you will be prompted to confirm the components to be imported.
If Reports/Options/Immediate is TRUE, the exported report components will be imported into the target application; otherwise an import script will be written and can be run via Reports/Batch Install.
Note: Reports/Options/Replace Existing:
• If TRUE will apply the '-m –nreplace' flag to the import without prompting for confirmation.
• If FALSE and name conflicts are detected, you will be given the option to Skip, Cancel Install, or Replace. Name conflicts can only be detected if the current application report list is up to date.