Re: ODBC, NT and Workgroup problem

A select statement running with dirty read isolation should not get a 243 error. It is not affected by locks. But dirty reads can have other problems like duplicate data. A select statement running with committed read or higher isolation and not in a transaction is not affected by SET LOCK MODE TO WAIT. If it encounters a lock record (data or index), a 243 error will be generated. Also, the error could be 243, 244, 245, 246 I hope that's clearer. Steve Berg On Fri, 23 Oct 1998, Jun Nolasco wrote: > Hmm. Are you saying that a select statement outside of a transaction > can get this error? Even on a dirty read setting? > > Thanks. > > > Jun Nolasco > > > ]Steve Berg wrote: > > > > BTW - SET LOCK MODE TO WAIT - only works for and update statement or a > > select statement inside a begin work - commit work. A select statement > > not inside a transaction will not wait. Therefore proper handling of the > > 243... error is important. > > >