This work-around only applies to the UniVerse RDBMS.
Due to an issue in the UniVerse RDBMS, the Kourier GUI will not allow net change to be enabled on an application file which also has a RDBMS trigger. Rocket software is working on a fix for this problem but until that fix has been released and verified by Kore, the following procedure may be used to enable net change on a file with an RDBMS trigger.
This work-around assumes that:
To enable net change on an application file which has an RDBMS trigger:
Normally when an application file is enabled for net change from the Kourier GUI, a "virtural" index is created in the application file's dictionary named KCL_INDEX. This dictionary calls a subroutine named KCL.UPDATELOG from the formula field (attribute 2) of the dictionary. This subroutine is responsible for maintaining the net change file associated with the application file.
With this work-around in place, if an application file has a trigger and the control item BYPASS.TRIGGER.ERROR is found in the KT_CONTROL file, Kourier creates an index named KCL_INDEX but it does not call the KCL.UPDATELOG subroutine (e.g. the formula field is set to ""). This effectively by-passes the UniVerse "bug" and indicates to the Kourier's run-time environment (e.g. services) that net change has been setup on the application file and that this file will be maintained thru the code you added to your trigger subroutine.
Kourier Integrator Setup and Administration Guide