>Question, I thought transactions worked against the table, not the view, so it would not truly work this way. Is that not so? If you create views on free tables and contain those views in a dbc, then transactions (and rollback) actually work as designed? If so, what is the performance hit?
>
>TIA,
>Tracy

Tracy,

Tableupdate() on a view updates the underlying table and if that fails the update for the view fails. That's why using the view will give the ability to have transactions.