Refer to documentation Implementation
Presentation
When entering the function, an entry screen is displayed used to define the data to extract and the setups applied to this extraction.
Validation starts the function, after a confirmation request in a box giving the following message:
| Number of tables to be integrated: NNN |
A log file is created and viewed in order to know the result (and any possible errors in the extraction).
Close
Fields
The following fields are present on this tab :
Block number 1
| Define the folder code, as it is defined in the folders table, in which the work will be carried out. |
| If the folder where the tables are integrated possesses an archive folder, there is the choice to integrate into the archive table (by checking the box) or in the table in the live folder (not checked). |
|   |
| Defines the name of the table to be integrated or a template characterising the name of the tables to be integrated. If for example, all the tables present in the SVG directory are to be integrated, all that is necessary is to enter * in this field. |
|   |
Block number 2
| When this box is checked, the file with extension cfg present in the SVG directory is used to define the table, taking into account the configuration directives such as the size of the extents. Its structure is described in an annex. |
| When this box is ticked, the sizing information (from the file with the extension srf) found in the integration directory is ignored and instead the information found in the FIL directory (if it exists) is used. |
Close
This function is linked to the adonix engine and not to the standard databases. As a consequence, it should not be used as a habitual backup procedure, since it does not have the guarantees of security or performance. A backup with the standard database tools is strongly recommended before every use of this type of function.
Amongst the limitations of this type of function, it should be noted that, if it is launched for several database tables, it can lead to a database image that is not globally coherent if updates take place during the export (unlike the standard tools associated with the databases). If the function is to be used to import all the tables extracted in a coherent way, it is necessary to ensure that nobody else is connected to the folder during the integration.
This function can be run in batch mode. The standard task DOSINTEG is provided for that purpose.
In addition to the generic error messages, the following messages can appear during the entry :
Error when accessing table AUTILIS
Non-existent file
This error message leans that the selected folder was not created or does not exist anymore (in any case, the user table could not be found in this folder).
At the time of the integration, a log file is created. Errors can arise: They appear in the form of an error line (in red) in the log file, followed by additional information.