>BACKGROUND:
>i have a form using a view (v_items).
>the view is updatable and only has one base table in it (items).
>this base table has an update trigger.
>buffering 5 is being used along with a TABLEUPDATE().
>
>what is happening is that on my form i change v_items.quantity and hit the update button which goes thru and fires the TABLEUPDATE().
>the first time i change the quantity and the trigger fires.
>in the case i'm testing the trigger fails because of a business condition not allowing quantity to change. the code then does a TABLEREVERT(.T.) on v_items.
>
>then while still on the form i change the quantity again and hit the update.
>this time the trigger isn't firing, even though the TABLEUPDATE() is occuring.
Is this business condition some kind of property value or something else that may not be getting reset so the trigger will fire?
Mark McCasland
Midlothian, TX USA