>Reason: SELECT - SQL re-opens the table, and the appended records don't yet
>exist on disk, until you issue TableUpdate().
>
>Workarounds:
>
>1) Save your changes with TableUpdate() first.
>
>2) Select the same workarea where you are doing changes, and COPY TO a temp
>table.
Workaround 2) was my preferred method, but there is another one.
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.
BEGIN TRANSACTION
TABLEUPDATE(2)
SELECT * FROM myTable
ROLLBACK