At 10:47 PM 1/5/2003 +0000, Didier Gasser-Morlay <Didiergm@...> wrote:

>Yes, I agree this is the way to go but I was hoping to be able to mark
>the record as deleted in a before delete trigger event and somehow
>prevent the actual deletion from happening.

Sigh. The right way to do this is to create a view and put a
trigger on the view that changed a delete to an update. However,
at some point, some bright spark decided to remove the code that
checked for view triggers and eliminated the "natural" action, so
you have to create a "non-updateable" view. With a non-updateable
view, you need triggers to handle inserts and updates as well
as deletes.


Regards,

Ann
www.ibphoenix.com
We have answers.