> I thought explicit transactions would not be affected by OAT
> processing. The help says:
>
> > An explicit transaction is initiated by calling the StartTransaction
> > method. It will persist until one of the methods to end the unit of
> > work is called.

The explicit transaction remains but the physical transaction, if not
flagged as active with an update, will still be eligible to bumped by OAT
handling.

If you want to get rid of OAT then set the Isolation to tiConcurrency and
this will stop it. This is because if you want a snapshot then the
transaction has to remain or else it would allow a new view to be created.

> So, does anyone think the help or the component is wrong in this
> regard, or it's just me? In the latter case, how can I setup a
> transaction that does not expire automatically?

It could be stated more clearly but it isn't wrong.

Regards,
Jason Wharton
CPS - Computer Programming Solutions
Mesa Arizona
http://www.ibobjects.com

-- We may not have it all together --
-- But together we have it all --