Application object (Manager)
Imports form definitions, set definitions, batch definitions, and tables to FORMS from a file, similar to the command (FORMS Help topic) on the menu. (If you do not want batch definitions, use ImportDefinitions.)
The name of the file from which definitions and tables are to be imported is specified in ImportFileName, and names of what to import are specified in the FormDefNames, SetDefNames, BatchDefNames, and TableNames parameters.
You can import several definitions of each type by separating each one with a space.
Example: "Form1 Form2".
An asterisk (*) can be used to include all the definitions in the import file.
The OverwriteType parameter specifies what happens when definitions to be imported are already present in the database.
0 – Do not overwrite. Specified definitions are ignored if they already exist in FORMS.
1 – Overwrite. Existing definitions are overwritten by those from the import file.
2 – Overwrite if safe. Existing form/set/batch definitions are overwritten only if there are no forms/sets/batches of that type present in the database.
|
Return value |
Description |
|
0 |
OK. |
|
1 |
Could not open file. |
|
2 |
The file is not a legal EHF file. |
|
3 |
The file is corrupt. |
|
4 |
The form definition database is not available. |
|
10 |
Failed to append name to form definition name list. |
|
11 |
The form definition name is too long. |
|
12 |
Failed to append name to table and set definition name list. |
|
13 |
The table definition name is too long. |
|
14 |
Failed to append name to set definition name list. |
|
15 |
The set definition name is too long. |
|
16 |
Failed to append name to batch definition name list. |
|
17 |
The batch definition name is too long. |
|
9985 |
BLOB read error. |