Failure of a trigger to record the data

[cbsethna]

Team
I have a program xxbmpsmt.p where in I call the standard program bmpsmt.p ( Product Structure Maintenance ) . Before the call I have triggers written to track the changes done by whom , when and what changes.
In one instance it happened that these triggers did not fire and system was unable to track the required changes.

What are the ways we can check why the trigger did not fire in progress OpenEdge 10.02B .

Regards
Cyrus Sethna

 

[TomBascom]

The correct answer is to update to a supported version of OpenEdge and to then use OE Auditing.

You claim to be running 10.02B which, so far as I know, is not an actual release. Did you perhaps means 10.2B? (no extra "0"). OE Auditing does exist in that version, it was introduced with 10.1B (about 20 years ago...)

If, OTOH, you really meant 10.0B you do not have OE Auditing available. In either case you are woefully out of date.

How do you know that an untracked change occurred?

When you say "record the data" do you mean that the trigger is writing something to a db table? Or are you logging your audit data externally?

There are several ways that that could fail:

1) Unless this is a FIND trigger (which makes no sense if you are tracking _changes_) then that trigger is almost certainly being fired during a TRANSACTION. if the transaction is undone then so will the trigger's recording of the change.

2) Somewhere in the code there might be a DISABLE TRIGGERS command...

3) Triggers only fire for 4gl events. If a change is made via a SQL connection (OBDC or JDBC) it is invisible to triggers.

4) Your code may be buggy.