Re: Disabling Commit and Update

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?

You don't explain what means are currently available to users. Or what version. Or much else. So I could offer ideas but they wouldn't necessarily be meaningful.

What I would like to dispute is the statement that some calculations are too complex for trigger: Nonsense!

Write the code as a stored procedure, either in the database or the form, and execute it from the trigger.

--
Daniel Morgan
http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)