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

Well, the ONLY way there will be a disconnect from VFP will be if YOUR CODE used SQLDisconnect.

If VFP crashes, so will the inproc ODBC driver.

If VFP crashes then your code certainly can't SQLDisc().

If VFP crashes then VFP code certainly can't send ODBC a commit.

If VFP the machine vfp is on crashes, same thing.

In all the above cases, the connection to the server will drop and the server will rollback automatically.

So, the ONLY way that I can see VFP sending a Commit to ODBC on disconnect is if it is RUNNING and you coded SQLDisc() on a connection with a pending transaction.

So, it SEEMS to me you don't want 'control' but you want protection from bad coding habits.

BOb