>3) Wrap the TableUpdate() in a BEGIN TRANSACTION/ROLLBACK so that you do the SELECT statement and then roll back your changes. I don't like this method, but there isn't any reason I know of not to use it.
>
>
>* Pseudo-code -- do not use unmodified.
>* Append records
>BEGIN TRANSACTION
>TABLEUPDATE(2)
>SELECT * FROM myTable
>ROLLBACK
>
Thanks: this is very interesting alternative.
I can imagine one good reason to use it: I don't want to save yet.
And one good reason not to use it: I understand that transactions use implicit record locking.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
