>Hi Patric.
>
>>An update trigger is failing for a table that has a compound expression as it's primary index...ACCOUNT+DTOC(REQ_DATE)
>
>The code generated by the RI Builder doesn't properly handle updates with compound keys (in fact, when you use the builder to generate the code, it warns you about this).
>
>You'll have to manually edit the update trigger code for the table to specifically do what you need.
>
>That's one of the reasons most database gurus strongly recommend using meaningless primary keys, such as automatically assigned integers. It completely avoids this problem.
>
>Doug

Thanks for the reply, Doug. You're absolutely right about the RI Builder warning, but unfortunately this problem is something I've inherited and was hoping to avoid establishing a new primary key, etc.

Since the delete trigger works fine, I just opted for creating my own code for updates... Not the best fix as far as technique, but it put the fire out for now. (This whole issue surrounds an application that is being phased out, so I think it'll will hold as a final solution!)

Thanks again,