Subject AutoCommit and TransactionState
Author (no author)
Hey there,

I am struggling to understand the implications of using AutoCommit=TRUE.

There is an application that uses this behavior but the problem is that before and after doing the auto-commit the transactions state is "ActivePending".
This means that some IBO-actions on a toolbar don't get notified (by their StatusChanged event) that a commit has happened.

Currently the problem is a "Save" button which should do a commit on the current transaction that is still active even when no more changes need to be committed.

More importantly, I'd like to understand a bit more about this behavior and if there is some way to control it.. comments in the source code for the "TransactionState" property say that after auto-commit the state could be either "Inactive" or "ActivePending" but I don't understand how this is decided.

Please help! :)


P.S.: I even started to entertain the idea to "simulate" the auto-commit behavior by manually doing a commit after post, but I don't see a way to go about it except for handling it on the query level..

[Non-text portions of this message have been removed]