>I clarified one thing: it is not the trigger that is executing but the table validation rule, which executes some code I wrote. What's happening is that while the table validation code is executing, the buffer is dirty, but as soon as control returns to the main program from the table validation code, the changes are applied. This is problem, as far as I can see... I didn't expect the changes to be applied until I do a commit.

Chaim,

The code in Table Rule (and field rule) is fired immediatelly in UPDATE. That's the correct behavior and by design. However, if you do TABLEREVERT your new changes should be reverted.

What exactly is a problem? Perhaps you wrote some dangerous code in this table rule changing environment settings?

We're using table rule to update Last Modified date and Last Modified User fields.