Well spotted, it is a typo in the message post, the actual keylinks
in TIBOQuery are correct.

Cheers,
Sean.

--- In IBObjects@yahoogroups.com, <carl.mcknight@...> wrote:
>
> I do not know if this is relevant by you have a typo:
>
> LOCTYPLU.LOCATION_TYPE
> LOCTYEPLU.LOCATION_TYPE
>
> ________________________________
>
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]
On
> Behalf Of Sean Palmer
> Sent: Friday, August 04, 2006 11:35 AM
> To: IBObjects@yahoogroups.com
> Subject: [IBO] Re: IBO 4.6Bc
>
>
>
> I do, I have the following SQL in a TIBOQuery...
>
> SELECT
> LOCATION.LOCATION_ID,
> ...
> LOCTYPLU.LOCATION_TYPE,
> LOCTYPLU.TYPE_NAME
> FROM LOCATION
> INNER JOIN LOCTYPLU ON (LOCATION.LOCATION_TYPE =
> LOCTYPLU.LOCATION_TYPE)
>
> The keylinks are correctly defined as...
>
> LOCATION.LOCATION_ID
> LOCTYPELU.LOCATION_TYPE
>
> I get an "Invalid KeyLinks entry: LOCTYPLU.LOCATION_TYPE."
exception
> when preparing the statement.
>
> This worked with IBO 4.6B
>
> Cheers,
> Sean.
>
> --- In IBObjects@yahoogroups.com <mailto:IBObjects%
40yahoogroups.com> ,
> Helen Borrie <helebor@> wrote:
> >
> > At 12:34 AM 5/08/2006, you wrote:
> > >I get the same problem with D2006 and TIBOQuery. I also get a
> > >exception with "Invalid KeyLinks entry:..." even though the
> keylink
> > >is the primary key of the table.
> >
> > For a joined set, you need (at least) the PKs of both tables.
> >
> > Helen
> >
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>