Re: Disabling Commit and Update

In article <f0e3dc0b.0307221347.daccc20_at_posting.google.com>, jim_esti_at_hotmail.com (Jim) wrote:
>As I said I could put the code in the various aspects. As you
>indicated that it would be ideal to have a simple procedure to handle
>the process and I agree.
>
>But it is not indicated that way in my specs.
>The specs indicate that all forms of COMMIT, UPDATE etc be removed and
>only the possible way to do any sort of commit, update etc would be
>through a POST button.
>
>The problem becomes when I null out the KEY-COMMIT or ON-UPDATE
>trigger and then call for a commit in the POST button it fails. It
>appears that the trigger catchs the commit. It must be due to the
>methods used in the button to do the actions.
>
>I have resorted to added:
>:global.trigger_disable := 'true'; -- added to the start of the POST
>Button
>:global.trigger_disable := 'false'; -- added to the end of the POST
>Button
>
>Then in the KEY-COMMIT, ON-UPDATE etc I added:
>
>if if :global.commit_disable = 'false' then
> message ('Commit not allowed here.');
>else
> commit;
>end;
>
>The tricky part comes when I do the on-update trigger.
>This simple trick will not work as easily as I update each row
>seperately and update different columns based upon special cases. The
>joy fun of it.

I'm missing something... how does the on-update trigger ever get fired without a pre-commit trigger being fired first? Try moving your disable logic to the pre-commit trigger. Received on Wed Jul 23 2003 - 14:29:15 CEST