The GUI and non‑GUI versions of the Schema Load utility (jadload and jadloadb, respectively) and the non‑GUI RootSchema JadeSchemaLoader application are supplied with the JADE release, to enable you to load runtime‑only JADE applications.
A set of Schema Load utility database files that contain no JADE development information is also supplied on the JADE release medium. The Jade Loader icon is installed in your JADE program folder when you install JADE.
The standalone Schema Load utility and the JadeSchemaLoader application enable you to load JADE applications into a cut-down database, which excludes all JADE development classes and methods. You can load:
User schemas into a runtime-only JADE database that can then be deployed at user sites
Patches to your JADE system into a full JADE environment or a runtime-only environment
Patches to a runtime-only database deployed at a user site
The Schema Load utility and the non‑GUI JadeSchemaLoader application enable you to:
Add new classes, interfaces, and methods
Modify existing methods
Rename schemas
Add, delete, or modify properties and inverse references
Delete existing schemas, classes, interfaces, packages, or methods
Reorganize user data
Load form, RPS database map, relational view, and external database definitions
Load JADE Report Writer data
As all JADE Report Writer files (that is, files with a suffix of rwv, rwo, rwf, rwu, rwr, and rwa) are loaded only into the current schema version, they should therefore be loaded after any database reorganization transition.
Exception 5012 is raised if you attempt to load a Unicode schema into an ANSI JADE environment.
You can run the JadeSchemaLoader application:
As a presentation (thin) client
In single user or multiuser mode as a standard (fat) client
In single user or multiuser mode from a non‑GUI client
From your application code