Subject | Re: [IBO] Why RDB$DB_KEY? |
---|---|
Author | Helen Borrie |
Post date | 2001-08-06T14:47:41Z |
At 09:18 AM 06-08-01 -0500, you wrote:
Without actually seeing the callstack, I'd guess you have a "weird" situation here because the keylinks entry isn't valid. It should simply be COUNTER. (A keylinks of COUNTER=COUNTER isn't any sort of valid; but if it was a lookup dataset linking to a Keysource, it would be COUNTER=OTHERTABLE.COUNTER).
Basically this can't be any sort of right if this dataset is a detail in a master-detail construction...
Regards,
Helen
All for Open and Open for All
InterBase Developer Initiative ยท http://www.interbase2000.org
_______________________________________________________
>Hi All,Steve,
> With a simple table: Counter=Integer, LastName=VARCHAR(30), etc.
>as OVERTIME.
> I have the primary key on COUNTER, a generator. In the program I
>have a TIB_Query with SELECT * FROM OVERTIME FOR UPDATE, KEYLINKS:
>COUNTER=COUNTER, MASTERLINKS:COUNTER=G_OTCOUNTER, the default
>ordering text (built by right-clicking), and the default SQL text
>generated with the default settings:Prepared Edit, Search Delete,
>Searched Edits.
> When I select the Generate For Table I get the three SQL texts
>but in the Edit SQL I get the normal setup but at the bottom I
>get WHERE RDB$DB_KEY = :DB_KEY
> From this point on I get errors of _Invalid Custom DML Column
>Reference RDB$DB_KEY.
> How do you fix this when it is the default?
Without actually seeing the callstack, I'd guess you have a "weird" situation here because the keylinks entry isn't valid. It should simply be COUNTER. (A keylinks of COUNTER=COUNTER isn't any sort of valid; but if it was a lookup dataset linking to a Keysource, it would be COUNTER=OTHERTABLE.COUNTER).
Basically this can't be any sort of right if this dataset is a detail in a master-detail construction...
Regards,
Helen
All for Open and Open for All
InterBase Developer Initiative ยท http://www.interbase2000.org
_______________________________________________________