>Thanks for you answer.
>
>Actually, my case is not about an invoice, so I can't avoid updating
>the fields of my view. The solution that come to my mind at this moment is
>to keep a reference of the record which is about to be deleted (the reference
>probably is gonna be the field I use to bond both tables), once the record is taken way from the table, then I can recall the record I want to keep by
>using the reference.
>Probably this will work but not reallly sure about the downsides of this
>procedure. I wanted to know the opinion of someone who had made this before
>or hear of a solution more pragmatic and elegant than mine.
>
>Thanks again, sorry for not being clear before.

Perhaps you should just delete in the underlying table.

Do you really need to make the record on the "parent" side updatable? Because if you don't, you would delete only the child record.

At least, I think so. I never worked with views that had updatable fields from more than one table, and it seems risky to me. I did use fields from other tables, but only as a reference, that is, R/O.

Hilmar.