Application object (Manager)
Exports form definitions, set definitions, batch definitions, and tables to FORMS from a file, similar to using ð in FORMS. (For more information, see Exporting definition and tables, a FORMS Help topic.) If you do not want to include batch definitions, use ExportDefinitions.
|
Parameter |
Description |
|
ExportFileName |
Specifies the name of the file to which definitions and tables are to be exported. |
|
FormDefNames, SetDefNames, BatchDefNames, and TableNames |
Specifies the names of the objects to be exported. Several objects of each type can be specified by separating them with a space. Example: "Form1 Form2". An asterisk (*) can be used to include all the definitions in the export file. |
|
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. |
|
5 |
General error (for example memory allocation or database error). |
|
6 |
Table record locked for updating. |
|
7 |
The set definition is locked by another Manager module. |
|
8 |
There is no set definition in the database. |
|
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. |