Execution
: Instead of database changes for texts in other languagesUse
This event occurs at the 'Save' function. A different logic from the standard can run, for example to also change hidden tables in the database.
Realization
The standard routine VIM_TEXTTAB_DB_UPDATE can be a template for the realization of the user routine.
The following global data is available:
·
internal table <VIM_TEXTTAB>: The text data handling in the user routine depends on the value of the processing flag·
ORIGINAL: no action required·
NEUER_EINTRAG: new entry. The entry must be put in the database and the processing flag set to ORIGINAL.·
NEUER_GELOESCHT: deleted. The entry must be deleted from the internal table. No database operation is required because the new entry does not yet exist there.·
GELOESCHT: deleted. The entry must be deleted from the internal table. The database deletion is in the entity save routine, so no database operation is required.·
AENDERN: change. The entry must be changed in the database. The processing flag is set to ORIGINAL.·
UPDATE_GELOESCHT: deleted. The entry must be deleted from the internal table. The database deletion is in the entity save routine, so no database operation is required.
If the
internal table <VIM_TEXTTAB> has been changed, the following statement must be at the end of the routine:
MODIFY VIM_TEXTTAB_CONTAINER INDEX VIM_TEXTTAB_CONTAINER_INDEX
.