Subject | Re: [IBO] KeyLinks AutoDefine |
---|---|
Author | Jason Wharton |
Post date | 2001-11-01T05:38:34Z |
No, it isn't easy to create because for me it works as expected.
There is something unique about your situation that isn't standard.
Please share more details of your circumstances.
PS. Your English is not a problem.
Thanks,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
There is something unique about your situation that isn't standard.
Please share more details of your circumstances.
PS. Your English is not a problem.
Thanks,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com
----- Original Message -----
From: "Artur Anjos" <arsoft@...>
To: <IBObjects@yahoogroups.com>
Sent: Wednesday, October 31, 2001 10:18 AM
Subject: Re: [IBO] KeyLinks AutoDefine
>
> Sorry, Jason, I mean to say 'DB_KEY'. It's the field that IBO creates when
it can not find a Primary Key to use as KeyField.
>
> In the example I told you, after Open the Query, I get the value 'DB_KEY'
in the KeyFields array, even if IBO don't create one.
>
> It's very easy to recreate:
>
> 1) Create a TIBOQuery and select just the Primary Key on any Table;
> 2) Set KeyLinksAutoDefine to true
> 3) Open the Query
> 3) Read KeyFields[0]: the value is always Name_Of_Table.RDB$DB_KEY
>
> So, two things:
>
> 1st) The value should be the name of the Field that IBO is using? In the
example above, if I put other field on the query that it's not unique, IBO
creates the field with the name "DB_KEY'.
>
> 2nd) What's the propriety in TIBOQuery to find out if the field is a
primary key? That will be enough for me: I will check if IBO created a
DB_KEY field: if so, I will use this field for my purposes, if not I will
choose the primary key field.
>
> Sorry about my english!
>
> Artur Anjos
>