> One thing I forgot to ask last night, when the transaction
> is active (transactionState=tsActive), then I can't pause
> it, even when the CommitChanges-Parameter is true. First
> I have to do a commit and then I can pause the transaction.
> Is this the right behaviour ?

A good question. Its been a while so I had to review the code. It
seems this was an intentional decision on my behalf. Pause checks
CanPause (see the GetCanPause function in IB_Transaction.IMP.

I think my logic was; a developer should be forced to take care of
committing or rolling back actual changes explicitly - since the
physical transaction is going to be closed. That, by default, Pause
should only really be used for closing transactions that are open for
reading.

You do have the ability to override this decision in the OnGetCanPause
event handler.

I am willing to consider comments/suggestions in this regard. I dont
who (if anyone) else is using Pause processing. Jason has done a lot
of work since this was coded, to reduce the need for explicit
developer actions. If anyone else is using Pause and has an opinion
in this matter, I would welcome the additional comments.

Geoff Worboys
Telesis Computing