Mark,

Isn't that the way TRANSACTION processing is supposed to work?

Seems to me that within your transaction you need the latest value for any given field all the while insulating those field changes from other users.

Good luck,

Jim N

>I am having fits making a transaction work. Code is:
> ... update data in form ...
> BEGIN TRANSACTION
> SELECT parent
> lSuccess=TABLEUPDATE(2,.f.,ALIAS(),aSaveErrors)
> ...
>
>I checked CURVAL() immediately before the tableupdate and immediately after. The table was UPDATED. I thought that BEGIN TRANSACTION created an additional set of buffers, TABLEUPDATE committed changes to those buffers, and END TRANSACTION committed those changes to disk. Here I see changes committed directly to disk - before END TRANSACTION is executed..
>
>The table in question was opened with Optimistic Row Buffering.
>
>Any ideas on what could be happening here? I have looked at this
>until I am numb.
>
>Thanks for any insight.