> -----Original Message-----
> From: Glen Parker [mailto:glenebob@nwlink.com]
>
> > > It appears there is a somewhat on-going bug in the ODBC driver
> > > (07.02.0005 in this case) concerning explicit transactions. The
> > > following sequence demonstrates it.
> >
> > What do you mean by explicit transactions ? i. e
> >
> > > Begin transaction (OK)
> >
> > How do you begin the transaction ?
>
> By turning off auto-commit with a call to SQLSetConnectOption().
>
> > > Execute update statement(s) (OK, records hidden from other
> > > transactions)
> > > Commit transaction (OK, records appear to other transactions)
> >
> > And how do you commit the transaction ?
>
> With a call to SQLTransact() to either commit or abort transaction.
Should SQLTransact() turn on auto-commit ?
regards,
Hiroshi Inoue
