>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.

That wouldn't make sense. The idea behind transactions is to be able to submit multiple DML commands to multiple tables.

Maybe at lunch today I'll fire up the Profiler and run quick test.

-Mike