Thanks Roman,

I posted that for someone else, and that sounds exactly like his description
of the problem.

Rick

----- Original Message -----

> > > Any idea what would cause a "lock conflict on no wait transaction
> > > deadlock" error?
> >
> > You have a isc_tpb_nowait in your TPB and two transactions has lock
> > conflict on some record. If you do not want to get this exception
> > immediately, but rather prefer to rely on server resolving the
> > conflict, remove isc_tpb_nowait from your TPB (or mapping).
>
> Sorry, maybe I was not very clear. You must have two transactions,
> one of which has modified the record, and another is either reading
> it (isc_tpb_read_committed & isc_tpb_no_rec_version) or writing it
> ((isc_tpb_concurrency ¦ isc_tpb_read_committed)), or you are using
> isc_tpb_consistency with isc_tpb_nowait. See page 67 of API Guide for
> more details.
>