Jason, but the keyfield is a property in the grid, not in the TDataset. I
compose it at run time with TDataset KeyFields values but the grid tries to
locate in this field calculated to synchronize the grid and the TDatset and
IBO give me an error.

----- Original Message -----
From: "Jason Wharton" <jwharton@...>
To: <IBObjects@yahoogroups.com>
Sent: Tuesday, January 08, 2002 4:54 PM
Subject: Re: [IBO] Locate in Calculated Fields


> After giving this a little thought, I believe it is a bad idea to have a
> calculated field acting as a KeyLinks field.
>
> Jason Wharton
> CPS - Mesa AZ
> http://www.ibobjects.com
>
>
> ----- Original Message -----
> From: "Miguel" <miguel@...>
> To: <IBObjects@yahoogroups.com>
> Sent: Tuesday, January 08, 2002 8:48 AM
> Subject: [IBO] Locate in Calculated Fields
>
>
> > I am testing developer express quantum grid with IBO and in the
> > groupping mode the grid needs a KeyField, besides when you select a row
it
> > performs a locate by this KeyField to synchronize the grid and the
> dataset.
> > I am having problems because my KeyField is composed and calculated in
the
> > fly and with other connectivity VCLs I could to locate by this field but
> IBO
> > gives me an error that it doesn't find the calculated field. Any idea? I
> > know that I could to setup a field and a generator but I think that I
> > wouldn't be earning any performance because I use a SQL order. Is there
> any
> > IBO property or IB to give me a KeyField or can I solve the Locate
> problem?
> >
> > Thank you very much.
>
>
>
>
>
___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or
InterBase
> without the need for BDE, ODBC or any other layer.
>
___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info
papers,
> keyword-searchable FAQ, community code contributions and more !
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>