The Patch Version Extract dialog is displayed when you select the Extract Patch command from the Patch menu in the JADE Installation Preferences dialog, to enable you to extract patch version changes made by all developers to a selected schema. The current JADE system release version is displayed at the top left of the dialog.
For details about extracting a range of patch version changes for a specific user or selected users, see "
To extract a patch version
In the Select Schema combo box, select the schema whose patch version you want to extract. You can select one schema only.
In the Extract Changes to Patch Number list box, select the patch number whose changes you want to extract. You can extract changes to only one patch version at a time. The current patch number is displayed, by default. The current (latest) source change made to a method in the specified patch version is extracted.
If your selected schema has subschemas and you also want patch version changes extracted for subschemas, check the Extract Subschemas check box. By default, patch version extraction applies only to the schema that you selected in the Select Schema list box; that is, you extract patch version changes to each subschema separately.
The Multi Extract File Name text box is then displayed, instead of the Schema File Name and Forms File Name text boxes.
In the Schema File Name text box, specify the name and location of the schema file that you want to extract; for example, c:\jade\bin\FaultPch2.scm. If you do not specify a location, the file is extracted to the current directory, with a default file prefix of the schema name and suffix of .scm.
For ease of identification, you should prefix your schema file name with the first few characters of the schema name followed by the patch version number, and with the appropriate suffix. For example, FaultPtch2.scm differentiates an extracted schema not only from the Faults.scm file but also from changes that might have been extracted from patch version 1 as FaultPtch.scm or FaultPch1.scm.
An error is raised if you are extracting the schema and you do not enter the name of a file or if an existing file cannot be accessed.
If you want to extract the schema to an existing file or you are unsure of existing extract file names or location, click the Browse button. The common File dialog is then displayed, to enable you to select the appropriate file or location, if required.
In the Forms File Name text box, specify the name and location of the form and data definition file that you want to extract; for example, c:\jade\bin\FaultPch2.ddb.
If you do not specify a location, the file is extracted to the current directory, with a default file prefix of the schema name and a suffix of .ddb
For ease of identification, you should prefix your forms file name with the first few characters of the schema name followed by the patch version number, and with a suffix of .ddb
An error is raised if you are extracting the forms and you do not enter the name of a file, or if an existing file cannot be accessed.
If you want to extract the forms to an existing file or you are unsure of existing extract file names or location, click the Browse button. The common File dialog is then displayed, to enable you to select the appropriate file or location, if required.
If you checked the Include Subschemas check box and you do not want the schema and subschemas patch version file extracted to the current working directory with a default file prefix of the schema name and suffix of .mul, specify the name and location of the patch version file that you want to extract (for example, c:\jade\patch3\MyPatch.mul) in the Multi Extract File Name text box.
The schema and each subschema are extracted to a separate pair of .scm and .ddb
For ease of identification if your file path does not indicate the specific patch number, you should prefix your extract file name with an identifiable name, possibly the first few characters of the schema name followed by the current patch version number.
If you want to extract the schemas and forms to an existing file or you are unsure of existing extract file names or location, click the Browse button. The common File dialog is then displayed, to enable you to select the appropriate file or location, if required.
Check the Remove History After Extract check box if you want to remove the patch history for your selected patch version after the source changes have been extracted.
By default, the patch version history is not removed after extraction. You can therefore still view a summary of changes that were made to a previous patch version even if the changes have been overridden by subsequent changes.
You can recreate a patch version history that you have removed, if you later want to see a summary of changes made in that patch version. For details, see "Recreating a History of Patch Version Changes", in the following section.
Click the OK button. Alternatively, click the Cancel button to abandon your selections.
Your selected patch version changes are then extracted and the change history for that patch removed, if applicable.
For details about extracting changes for a range of criteria (users, versions, and dates), see "
Only the changes made in a schema for the specified patch version are extracted, and not the whole schema.