>Details: I have an SQL Server as back-end. Lets assume, I have 5 cursors with some changed data and I want to save the data to the SQL server with 5 TableUpdates(). When will these changes be "commited" finally, i.e. will be placed into the resp. tables within the SQL server? With each TableUpdate() or only after all reported "Could be done" (returned 5 times .T.), i.e. after the End Transaction?
>Unfortunately I did not find anything, which helps me to decide, what to do...
>
>Any help appreciated.
>
>Hans


begin/end trans and rollback in VFP are valid for DBC tables in single
DBC container.
Buffering(5) tableupdate/Tablerevert is separate mechanisam which can (best way IMHO to) be effectively coupled (wrapped within) begin/end transaction but they are not dirrectly triggering each other.

Commiting to remote database is another story and it is not affected by
above decribed.


From VFP6 help topic 'Programming for shared access'
<snip>
Note When using data stored in remote tables, transaction commands control only updates to the data in the local copy of the view cursor; updates to remote base tables are not affected. To enable manual transactions on remote tables use SQLSETPROP( ), and then control the transaction with SQLCOMMIT( ) and SQLROLLBACK( ).
<snip>

HTH