Subject | RE: [IBO] Re: TIB_Cursor and DB_KEY |
---|---|
Author | Jason Wharton |
Post date | 2006-06-09T18:29:43Z |
There's a property you can set to tell IBO you don't want the KeyLinks
automatically defined for you. If you don't set the KeyLinks property then
IBO will do its best to find a way to uniquely identify each record of the
output. Set KeyLinksAutoDefine to false and it won't introduce the DB_KEY
column for those purposes.
Jason Wharton
automatically defined for you. If you don't set the KeyLinks property then
IBO will do its best to find a way to uniquely identify each record of the
output. Set KeyLinksAutoDefine to false and it won't introduce the DB_KEY
column for those purposes.
Jason Wharton
> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of clivewalden
> Sent: Friday, June 09, 2006 11:24 AM
> To: IBObjects@yahoogroups.com
> Subject: [IBO] Re: TIB_Cursor and DB_KEY
>
>
> Well (respectfully) that is an explanation without an answer<s>.
>
> Three things:
> 1. As far as I can see, a read only, uni-directional cursor has no
> need of a DB_KEY.
>
> 2. It should be controllable by the developer.
>
> 3. If IBO is going to return a hidden field for its own benefit, that
> I did not request in my SQL, then it should not impact properties like
> FieldCount. It should stay hidden.
>
> Just my 2 cents.
>
> Clive