Hi Mike ---

I don't think it's doing that now. Had an interesting "accident" yesterday that actually taught me something. Had to send several UPDATE statements to the same row in the same table via SQLEXEC with manual transactions. I forgot to put SQLCOMMIT in the code. Anyway, all of the UPDATES were posted to the db except the last one. So I suspect that what we're looking at is one open transaction at any given time, serialized, that is committed automatically if another command is sent. At least that's my read.

>
>Be careful with VFP 'manual SQL transactions' on SQL Server. I haven't checked to see if the implementation has changed, but when I got bit, VFP was enabling SQL Server implicit transactions connection setting. This means that any DML command causes a transaction to begin and you have to explicitly terminate the transaction. But the next DML command will again start a transaction. The implicit transaction setting is not reset until you disable VFP's manual transactions.
>
>-Mike