Re: Disabling Commit and Update

[Quoted] I am using Forms 5.

I have have disabled the key-commit feature via a trigger.

The issue remains that say a user re-queries or does some other action the form often ask if they would like to save the changes. I never want to allow the user a chance to save the changes by any onther means than the POST button provided.

Here is exactly what I am doing.
[Quoted] The user queries the table and then they can change selected values in the some columns. When they hit the post button it only looks at row that have changed and copies those into AUDIT if certian conditions are meet. If the conditions are not meet the row is rejected is reverted back to the orginal values while the other rows are updated on the primary table (and a copy is dropped into an audit table). The only way a row can be updated is if these certian conditions are reached. It works on a row by row case - not the entire table at once.  This is why I can not have a general update or commit of the entire table. The post button processes only the rows that have changed from the orginal and if the new values is valid then it just updates that particualr row and places a copy in the audit table. Warnings are giving about the particular row(s) that can not be updated/audited.

This is significantly different than just writting a simple on-update or on commit trigger. I know I could simiply could put the code behind the on-update, on-commit, etc but I would rather just diable those possiblites and only allow the changes to occur via the post button.

"kn" <keldn_at_kill.spam> wrote in message news:<3f1c6205$0$32511$edfadb0f_at_dread16.news.tele.dk>...
> "Jim" <jim_esti_at_hotmail.com> wrote in message
> news:f0e3dc0b.0307211014.3b7ee8f1_at_posting.google.com...
> > 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?
>
> key-commit, key-updrec triggers which will do nothing (null;)
> tool bar ? can't remember what cathes those ones,
> hopefully the same triggers.
> Is this homework, if I my ask ?
> If you are able to try it out from a home pc, then download the
> software from otn.oracle.com (read the license conditions!)
Received on Tue Jul 22 2003 - 14:39:19 CEST