Chaim,

Are you insisting on row buffering? I prefer to use table buffering, because otherwise you may have accidental updates when you move from the record...

BTW, I sent you a private message.

>I am experiencing a strange problem...
>
>I have a buffered table (optimistic row locking). I want to update it directly (that is, not via a view) and then commit the changes.
>
>However, what's happening is that immediately after I issue the update, the update trigger executes and commits the changes before I have a chance to issue the commit manually.
>
>I know the update is committed because I issue GETFLDSTATE. Within the update trigger, GETFLDSTATE indicates that the changes have not been applied. But immediately after the update trigger returns .T., GETFLDSTATE indicates that the changes have been applied.
>
>I have never seen this behavior before so I am mystified.
>
>My understanding was that the update trigger should not be executed after the update since the table is buffered. Is this correct? If it is correct, how can I figure out why the update trigger is executing?
>
>Thanks.