Hi Fabio,

You need both transaction commands. It is not a bug.

The VFP transaction command keeps the VFP *cursors* in synch with what happened in SQL Server. So, if the transaction was rolled back in SQL Server, you should roll it back in VFP as well to let VFP know that the VFP *cursor* has not been updated.


>Hi Hector,
>
>I have read to that article much time ago. Tanks!
>
>I have report this for your information and your comment.
>
>BEGIN TRANSACTION
>is un work around.
>
>If I do not have local data changed, why i have to do BEGIN TRANSACTION
>( it is a semaphore for not exit !).
>
>Moreover, BEGIN TRANSACTION is scoped to datasession, not nominative
>(type BEGIN TRANSACTION transName ),
>then background update, two or more suspend update are impossible on one datasession.
>
>For me this is a big bug.
>
>( IF @@TRANCOUNT>0 ROLLBACK is correct )
>
>Fabio