Kevin, he seems to be using IBX.
In the old days, IBO compatibility components used the TIBxxx form, but
since Ravi took over it without any respect, Jason changed those to TIBOxxx
and the native components are as ever TIB_xxx in IBO.
Unless Pablo is using a rather old IBO, I think he's using IBX. Another
proof: IBO doesn't have TIBUpdateSql component because it doesn't need it,
so this is definitely IBX.

Pablo, try to access the borland.public.kinobi.ibexpress NG in the Borland
news server at forums.inprise.com or newsgroups.inprise.com.

C.

> -----Original Message-----
> From: Kevin Stanton [mailto:kstanton@...]
> Sent: Lunes 12 de Junio de 2000 17:25
> To: IBDI@egroups.com
> Subject: RE: [IBDI] I'm having problems with Interbase 6
>
>
> I don't think the problem is w/ IB 6 but possibly Interbase
> Objects instead.
>
> What query component are you using: TIB_Query or TIBOQuery?
>
> I belive both support RequestLive.
>
> I have never used IBO's cached updates.
>
> For simple update forms that have a short life, I set the
> Autocommit to True
> and the isolation to tiCommitted.
>
> For posting routines, I take total control over the transaction.
>
> HTH,
> Kevin
>
>
>
> > -----Original Message-----
> > From: Paulo Albuquerque [mailto:paulo.albuquerque@...]
> > Sent: Monday, June 12, 2000 1:59 PM
> > To: IBDI@egroups.com
> > Subject: [IBDI] I'm having problems with Interbase 6
> >
> >
> > Can anyone help me ?
> >
> > I have moved recently to Interbase 6 (I used to use Paradox) and I
> > don't know how I have to work on it for best performance and less
> > problems.
> > I'm using a IBDatabase (Dialect 3) and a IBTransaction with the
> > following parameters:
> > - read_committed
> > - rec_version
> > - nowait
> > So I connected all my IBQuery to the IBDatabase. Then I noticed that
> > this component does not support RequestLive. So I attached a
> > IBUpdateSQL to each IBQuery. In that way the users change the data.
> > Is it the best way to let the users update their data ?
> >
> > There is something wrong with that configuration because I get this
> > error when more than two users try to access/update the same record...
> >
> > "lock conflict on no wait transaction attempt to store duplicate
> > (visible to active transactions) in unique index "INDEX_NAME" "
> >
> > Is this error caused by IBTransaction configuration ? Which are the
> > best parameters ? Do I have to use STARTTRANSACTION, ROLLBACK,
> > COMMIT ? When ? Where ?
> >
> > Thank you very much in advance,
> > Paulo Albuquerque
> >
> >
> > ------------------------------------------------------------------------
> > Take your development to new heights. Work with clients like Dell and
> > pcOrder. Submit your resume to jobs@.... Visit us at
> > http://click.egroups.com/1/4358/4/_/679568/_/960843565/
> > ------------------------------------------------------------------------
> >
> > Community email addresses:
> > Post message: IBDI@onelist.com
> > Subscribe: IBDI-subscribe@onelist.com
> > Unsubscribe: IBDI-unsubscribe@onelist.com
> > List owner: IBDI-owner@onelist.com
> >
> > Shortcut URL to this page:
> > http://www.onelist.com/community/IBDI
> >
>
>
> ------------------------------------------------------------------------
> Take your development to new heights. Work with clients like Dell and
> pcOrder. Submit your resume to jobs@.... Visit us at
> http://click.egroups.com/1/4358/4/_/679568/_/960845062/
> ------------------------------------------------------------------------
>
> Community email addresses:
> Post message: IBDI@onelist.com
> Subscribe: IBDI-subscribe@onelist.com
> Unsubscribe: IBDI-unsubscribe@onelist.com
> List owner: IBDI-owner@onelist.com
>
> Shortcut URL to this page:
> http://www.onelist.com/community/IBDI
>