.
This deletion is of course possible only if the "referential integrity" constraints as defined in the data dictionary, are adhered to, depending on the situation. These controls can take a relatively long time to perform, and they are carried out immediately, on-line when the delete function is called.
Obviously, if several deletions are to be performed, it would be very time consuming to run them one at a time. It is for this reason that the deferred deletions function is preferred for multiple deletions. The deferred deletion loads a database table, which store all the current deletion requests.
The Deletion function is used on one hand to view and modify these requests, and on the other to start the deletion of the queue of requests waiting to be processed.
Presentation
When using the function, a grid is displayed containing the current deletion requests in the form of the object code and the values of the keys.
It should be noted that when the key for the record managed by the object has a single part, only the first column is entered ; However, if there are two parts to the key, the first part is located in the second Identifier column, and the second part (which in general is the most meaningful) in the first.
The following possibilities are then available :
At the end of execution the deletion operation creates a log file giving the results of the operation.
Close
Fields
The following fields are present on this tab :
| This code identifies the object that manages the record that must be deleted. |
|   |
| Defines the key (if necessary composed of several parts) identifying the record whose deletion has been requested. |
|   |
| Enter the description of the relevant record. This long description is used as a title in screens and reports. |
|   |
|   |
|   |
Close