Re: ADO,ODBC and transaction

"Sheridan" <gh_at_hakom.at> wrote in message news:9ie%8.4$Eh.190_at_stuart.coltnet.at...
> I thought the sense of ADO is to be database undependent (at least for
easy
> things like updates or inserts)

Updates and inserts do work.

> and the IsolationLevel method of the ADO.Connection object should
> encapsulate the transaction level
>
> If this easy things doesn't work the complete ADO can be forgotten in
> muliple user enviroment

I wouldn't advocate abandoning ado, but just abandoning the goal of database independence. If you are targetting Oracle then target it. if you are targetting sql server then target that. Don't try for both unless you want to fall short of what either can do for you.

Your problem with isolation level is symptomatic of this approach. oracle is designed so that readers only ever see committed data and never block writers. Other products differ.

--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************