Hi Bob,

because i want a implicit protection,
also regarding a whichever bug that was present in VFP or my program.

If VFP succeeds to close itself and to make SQLDISCONNECT without my control,

I want that the transaction makes rollback.

Obviously, I can intercept ON SHUTDOWN, and execute a SQLROLLBACK() for every open logon;

but to me this is not enough, 

I want that even if VFP skip my control code for ON SHUTDOWN
(for a disowned reason to me),

VFP you do not make the COMMIT.

If VFP do not make COMMIT, ODBC and SQL Server do not make COMMIT
I have kill my application, powerdown Client PC, cut network wire,
powerdown server, .... any possible external problem,
SQL Server is good.

I dont want control the blackout, i want prevent the backout.

Fabio