You can load (install) an extract file into the current schema at any time; for example, when you are:
Restoring a full or partial schema
Passing code to another JADE developer
Fully reconstructing a schema in the same JADE release
You can load:
A full or partial schema or multiple schemas extracted to a single file
Forms in a schema
An extracted schema view
An extracted class, method, primitive type method, external database schema, relational view, RPS mapping, .NET exposure, or ActiveX type library
Patch version changes
For details about the order in which files should be loaded into a deployed database, see "
You can load a schema or forms file separately, if required.
A schema view is not set to the current view during the load process. (For details about setting a schema view, see "Setting a Schema View", in Chapter 3.)
If you have mapping logic on subclassed controls, other processes such as the JADE Painter, Translator utility, or the loading of schemas may also execute that logic. The logic therefore may need to perform checks to determine if it is running in the user application environment, to ensure that exceptions are not generated in these other situations.
As schema and forms definition files are treated as binary files, if the File Transfer Protocol (FTP) is used to transfer schema and forms definition files between machines, you must ensure that the transfer is done in binary mode (rather than ASCII) to prevent the removal of carriage return characters and the failure of the schema load process, particularly when schemas are encrypted.
You can also load an external database schema, ActiveX type library, relational view, or an RPS mapping. For details, see "
If a schema load is attempted when a reorganization is in progress (regardless of whether the reorganization progress dialog is displayed), the load fails. For details about reorganizing schemas, see "Reorganizing Your Schema", in Chapter 3.
You can load form and data definitions in XML Device Data Exchange (DDX) format instead of the Device‑Dependent Bitmap (DDB) format when the Use DDX style (xml format) as Default instead of DDB check box on the Schema sheet of the Preferences dialog is checked (it is unchecked, by default) and form and data definitions were extracted with the Extract Forms/Data as XML (ddx file) check box on the Extract dialog checked.
The XML format does not include JADE oids. All entities are identified by name and by their position in the XML object hierarchy. You can compare the DDX file to another version of the file, to identify what has changed between the two versions.
The first line of a .ddx file has the <?xml... header. The format of the second line is:
<schema name="schema‑name" JadeVersionNumber="JADE‑version" JadePatchNumber="patch‑number" CompleteDefinition="true|false">
The following is an example of the first and second lines of the XML file.
<?xml version="1.0" encoding="utf-8"?> <schema name="CalculatorSchema" JadeVersionNumber="18.0.01" JadePatchNumber="0" CompleteDefinition="true">
The schema name, which specifies the schema the information is for, must be included.
The JadeVersionNumber tag identifies the version of JADE that was used to produce the file.
The JadePatchNumber tag specifies the patch number to use for the load; otherwise the current patch number is used.
The CompleteDefinition tag, which must be present, specifies whether the file is a complete definition for the whole schema or it is a partial schema. If the value of the CompleteDefinition tag is true, any existing entities not included in the file are deleted.
The form and data definition (.ddb
******Warning: Control name on form name has no form control reference.
Ensure that the schema metadata (scm) and form and data definition (.ddb