Re: Disabling Commit and Update

In article <f0e3dc0b.0307220439.5d4dd7d0_at_posting.google.com>, jim_esti_at_hotmail.com (Jim) wrote:

>Here is exactly what I am doing.
>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.

Seems to me that this could largely be accomplished via database triggers without substantially altering Forms' default behavior... and probably requires less coding. Received on Tue Jul 22 2003 - 17:12:09 CEST