Specifying Advanced Load Options
The Advanced Load Options dialog, shown in the following image, is displayed when you click the Advanced button in the Load Options dialog.
The Advanced Load Options dialog enables you to specify a different target schema, the merge option for a partial schema, and the checking out of methods during the load.
If you are loading multiple schemas, the combo boxes in the Change Target Schema group box are disabled.
To specify your advanced load options
-
In the Target Schema combo box of the Change Target Schema group box, specify the new name for your schema or select the name of an existing schema from the list box name if you want to load into a schema other than the one defined in the schema file. This combo box is disabled if you are loading multiple schemas.
-
If you specified the name of a new schema in the Target Schema combo box, you can define its superschema, if required, by selecting the appropriate schema in the Subschema of combo box. (The Subschema of combo box is disabled if you specify the name of an existing schema in the Target Schema combo box.) This combo box is disabled if you are loading multiple schemas.
-
The options in the Schema Merge group box enable you to control the deletion of schema elements that are defined in the database but are absent from the schema file.
The Confirm before deleting option button is selected by default; that is, you are prompted to confirm that any schema element defined in the database but absent from the schema file is deleted from the existing schema. For more details, see "Merging a Schema in the Load Process", earlier in this chapter.
Select the Always delete (no confirmation) option button if you want to delete from the existing schema each element defined in the database but absent from the schema file. If this option is selected, you are not prompted for confirmation.
Select the Never delete (no confirmation) option button if do not want to delete from the existing schema any element defined in the database but absent from the schema file. If this option is selected, you are not prompted for confirmation.
For more details, see "Confirmation of Deletion", earlier in this chapter.
-
If a delta is set and it contains methods checked out prior to a schema load, they are updated with any change in the schema file.
If you want to preserve your current system, set a delta with no methods checked out prior to a schema load, and make sure the Check Out Methods check box is checked (it is checked by default if a delta is set). Any changes to existing methods are then checked out to the currently set delta.
The Check Out Methods check box is disabled if no delta is set in the schema.
-
In the Override Incoming Patch Numbers With text box, specify a value in the range 1 through Max_Integer - 1 (that is, 2,147,483,646) if you want to override patch versioning in incoming schema entities. All entities loaded in the schema file then have their patch version number set to the specified value. When you specify a valid value, it is effective regardless of whether patch versioning is enabled for the schema.
If the
The specified value does not have to match an existing defined patch number. If the value is the same as an existing patch number, the state of the existing patch version is ignored (that is, the existing patch number in the schema file is closed).
If patch control is enabled, the patch history will be stored. In addition, if patch control is enabled, the patch number set for a schema or a user is not affected by the override patch number, which is used only for the duration of the load process.
The default value for the override patch number is the patch number set up for patch control. If patch control is disabled, the default value will be blank (that is, there is no override).
-
Check the Allow Circular Packages check box if you want to allow a circular dependency between packages in the schema hierarchy; that is, to permit the loading of an incomplete package (for example, Schema1 exports Package1 and imports Package2, while Schema2 exports Package2 and imports Package1).
When you subsequently create a package that would result in circularities, you are prompted to confirm that you want to continue and allow a circular dependency between packages in the schema hierarchy.
By default, this check box is unchecked; that is, the packages that are available for import are those that would not result in circular dependencies in the schema hierarchy.
If you load two schemas that are not circular and you load an importer before the exporter:
-
An incomplete schema is loaded.
-
The form and data definition file (.ddb
-
Exception 8527 (Load results in one or more incomplete schemas) is raised.
When the
Incomplete schema definitions and their usages are resolved by loading the export definition and then reloading the importing files. (To completely resolve all of the interdependencies, more than two iterations may be required.)
An incomplete schema is displayed with the background color of a versioned schema (which defaults to red) in the Schema Browser. The incomplete schema, its subschemas, Class Browser, and any wizards for that schema and subschemas, are not available. To make the Class Browser available, it is your responsibility to make the entire schema complete (by loading the exporting schema and then reloading the incomplete schema).
An incomplete schema can be versioned, changing the background color, and not allowing the opening of a Class Browser on either version.
-
-
Click the OK button to confirm your selections. Alternatively, click the Cancel button to abandon your selections.
The Load Options dialog is then displayed, to enable you to change or confirm your load options.
If you changed the name of your target schema to the name of an existing schema that exists in the specified superschema, the schema is merged into the existing schema when it is loaded. For details, see "Merging a Schema in the Load Process", earlier in this chapter.
