Subject | RE: [IBO] TIB_Query - weird problem |
---|---|
Author | Helen Borrie |
Post date | 2003-12-10T09:53:10Z |
At 10:39 AM 10/12/2003 +0100, you wrote:
How come FH_UNIEK is the primary key, yet fh_bonnr is getting the generated
number? (curious...)
Put the PK in the query, and take out "for update" and you should get
somewhere (it doesn't do what you apparently think it does...)
Helen
>Ok here it isAm I blind, or do I really not see FH_UNIEK in your column list?
>
>The sql:
>select
>FH_REF1,FH_CODE,FH_OLDCODE,FH_AFD,FH_BONNR,FH_FAKNR,FH_BHLINK,FH_KLNR,FH
>_AUTO,FH_KILOM,FH_BVW,FH_VZW,
>
>FH_AGT,FH_CRDAT,FH_AFDDAT,FH_VDAT,FH_BONDAT,FH_FAKDAT,FH_KORT,FH_VOORS,F
>H_WBET,FH_SEL,FH_LEVNM,
>
>FH_LEVPST,FH_LEVSTD,FH_LEVLND,FH_BTWEX,FH_REF2,FH_SLOT,FH_VOOR,FH_TOTPR,
>FH_CONTP,
>
>FH_STATUS,FH_PROJ,FH_VORD,FH_EXT1,FH_EXT2,FH_EXT3,FH_DEBLINK,FH_BV,FH_UN
>IEK,FH_AFGEH,FH_MNT,
>
>FH_KOERS,FH_AFGEWERKT,FH_FACTUREREN,FH_CONTAN,FH_AP1,FH_AP2,FH_AP3,FH_AP
>4,FH_EENHEID,
>
>FH_AFMETING,FH_LEVTAV,FH_AUTOV,FH_PLAAT,FH_INTRASTAT,FH_TRANSPORTEUR,FH_
>WEEKLEV,FH_REF3,
>
>FH_LEVADRES,FH_LEVSTR,FH_KORTING,FH_LEVSTR2,FH_REFERENTIE,FH_STR3,FH_MIN
>PR,
> FH_INTRA2,FH_KORTKLANT,PROJECTOMSCHRIJVING,FH_DATAFH,
> KL_NAM,KL_OPV,KL_STR,KL_WPL,KL_TEL,KL_FAX,KL_TAV,KL_AFD, fh_info
> from csfhpx where (fh_code= 'B') for update
>
>Requestlive is true, fetchwholerows is false
>IBO version is 4.2.I Interbase version is WI-V5.6.0.29
>
>the calculatedfields are
>
>selectie varchar(80)
>nieuw varchar(3)
>gefact varchar(1)
>af varchar(1)
>
>But any calculatedfield gives the problem, even without any event
>defined on the query.
>
>no updatesql defined
>keylinks is FH_UNIEK (which is unique)
How come FH_UNIEK is the primary key, yet fh_bonnr is getting the generated
number? (curious...)
Put the PK in the query, and take out "for update" and you should get
somewhere (it doesn't do what you apparently think it does...)
Helen