Re: Disabling Commit and Update

I'll forego comment on the sensibility of what you're doing, as I'm sure others will comment, and just offer you a very simple method to accomplish what you're asking: use a global variable to "flag" the commit (or pre-commit) trigger... set it to "true" before committing, and have the trigger set it back to "false."

In article <f0e3dc0b.0307211014.3b7ee8f1_at_posting.google.com>, jim_esti_at_hotmail.com (Jim) wrote:
>Hello,
>
>I have a basic form and a post button.
>The user is able to view and query a particular table.
>
>When the user presses the post button some calculations are done and
>the table they where looking at is updated via the post button only.
>The calculations and features behind the post button are to
>specialized and complex to do via update trigger or commit trigger.
>
>I can write the post button so that it updates the table correctly.
>What I want to do is disable the user's ability to Commit and Update
>that table via another means than that post button. When I try to add
>triggers to the block the Commit and Updates it effects the updates
>and commits I do on the POST button.
>
>How can one disable the Commit and Update keys/process and yet be able
>to do the same functionality on a button? The only way I want to let
>the user Commit or update is via this post button.
>
>Any Ideas?
Received on Tue Jul 22 2003 - 16:57:59 CEST