Re: After Insert/Update trigger question

UPDATE_CEDR_CUSTS simply reads the SAME table : this is not allowed in triggers. Don't you have already all values available.
If not the general strategy is to buffer the primary keys in a pl/sql table and to process whatever you need to do in an after statement trigger.

Hth,
Sybrand Bakker, Oracle DBA

Ken Halsted <kenman_at_mail.snider.net> wrote in message news:sam7f4ue2pd168_at_corp.supernews.com...
> I have this trigger on table: AR_CUSTOMERS:
>
> --------------------------
> CREATE OR REPLACE TRIGGER T_CUSTOMERS_AIUR AFTER INSERT OR UPDATE
> ON AR_CUSTOMERS
> FOR EACH ROW
> BEGIN
> UPDATE_CEDR_CUSTS(:NEW.CUSTOMER_NUMBER);
> END;
> ------------------------
>
> UPDATE_CEDR_CUSTS simply reads the SAME table based on the customer number
> and updates another table in our database with some of the info.
>
> I keep getting an error when I update or insert a record from the form
 based
> on AR_CUSTOMERS but if I run the procedure stand-alone, it works fine.
 Any
> suggestions?
>
> Thanks for any help,
>
> Ken.
>
>
>
Received on Thu Feb 17 2000 - 00:00:00 CET