But is there something wrong with my query? Why can't the LockSQL be
generated?

Riho-Rene Ellermaa
senior programmer
Hansabank

>
> Yes, you should create it yourself if IBO cannot determine it for you.
>
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
> ----- Original Message -----
> From: "Riho-Rene Ellermaa" <r.ellermaa@...>
> To: "IBObject (E-mail)" <IBObjects@yahoogroups.com>
> Sent: Tuesday, October 16, 2001 4:03 AM
> Subject: [IBO] LockSQL
>
>
> > It's hard to get the answer.
> >
> > When my app gets error "Unable to initialise default LockSQL", then
> should
> > I create it myself? I want to disable users possibility to
> edit the record
> > from 2 places simultaneously.
> >
> > Query:
> > SELECT id,(select account from account a where
> a.id=dom_pay.accid) as
> > accountno
> > , ACCID
> > , STATUS
> > , BBANK
> > ...
> > , VER
> > , SIGN1
> > , SIGN2
> > , BANK
> > FROM account
> > join dom_pay on account.id=dom_pay.accid
> > where uid=:UID and install=:INST
> > for update
> >
> > KeyLinks:
> > ID
> > ACCID
> > STATUS
> >
> > PessimisticLocking=true
> > Keylinksautodefine =false (was true - same results)
> >
> > How can I make the IBO4.2Eb to create LockSQL automatically?
> >
> > Riho-Rene Ellermaa
> > senior programmer
> > Hansabank
> >
> >
> >