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.





>>Hi
>>
>>I got a view formed by two tables and the user is allowed to update all the fields of it.
>>What is the most elegant and pragmatic way to delete records from this view but only one of the source tables gets it records deleted ( this is something like the details of an invoice)?
>>
>>Thanks in advance
>
>I think you should only make the fields from the invoice-detail table updatable. Thus, the parent table should be untouched. You would include the parent table, to show additional fields - but you don't edit or delete them directly through the view. Look at the view update criteria (criterios de actualizacíón).
>
>Saludos, Hilmar.