>
>Begin..End transaction doesn't free you from writing tableupdate() if buffering is used or data won't be updated. Think begin..end transaction as interactively executing a series of commands. If you rollback at a point it means you didn't executed any of these (if supported by transaction). With or without transaction you would write tableupdates as necessary (end transaction doesn't make tableupdate). If you don't tableupdate or revert at a point it means like you quit or close the table without committing by update or revert. In case of issuing a rollback you don't need a tablerevert because you didn't do something to revert (rollback rolls you to the beginning)
>One last thing, with transcation it doesn't differ if buffering is on or not and you can use a series of nested transactions (up to 5 currently).
>Cetin

Thanks, I have tried to write something using these commands, and I am now much much more clear about these. But one more thing I would like to ask about tableupdate. It seems that the content change by tableupdate is still not permanent. It still can be undone with rollback, right?

Regards,
Ron