J
JohnO
Hi all,
I'm new to vba and adodb so apologies if this is a dumb question
but...
I'm submitting SQL to DB2/400 from an Excel macro, using the Execute
method of the Connection object. This works fine and dandy.
I also use the CommitTrans and and RollBackTrans methods of the
Connection object, but they don't operate as I expected. I notice that
when I change some data, that change is visible to other users on the
database. From my background with other SQL databases, I would not
expect other users to see the changes until after the transaction is
committed. At this point I figured it must be in some sort of
AutoCommit mode, but the RollbackTrans operation does work, so that
can't be the case, can it?
The ODBC datasource has commit mode "Read Uncomitted" - not sure what
that means.
So how does the RollbackTrans really work - does it use client side
buffers, or does it use the native database?
Thanks & regards,
JohnO
I'm new to vba and adodb so apologies if this is a dumb question
but...
I'm submitting SQL to DB2/400 from an Excel macro, using the Execute
method of the Connection object. This works fine and dandy.
I also use the CommitTrans and and RollBackTrans methods of the
Connection object, but they don't operate as I expected. I notice that
when I change some data, that change is visible to other users on the
database. From my background with other SQL databases, I would not
expect other users to see the changes until after the transaction is
committed. At this point I figured it must be in some sort of
AutoCommit mode, but the RollbackTrans operation does work, so that
can't be the case, can it?
The ODBC datasource has commit mode "Read Uncomitted" - not sure what
that means.
So how does the RollbackTrans really work - does it use client side
buffers, or does it use the native database?
Thanks & regards,
JohnO