Subject | Re: [IBO] cascade relations |
---|---|
Author | Gediminas |
Post date | 2003-08-24T19:53:24Z |
Paul,
when trying to scroll Dances LisbBox, got exception "Dataset cannot
scroll". I suspect, that KeyLinks & KeySource fields must be set not in
qryDancesLookup, but in the qryClassDancesDet. Am I right, that lookup
dataset is parent?
Thank's for such detailed answer - really helpful. GSG would be great, but
it is not affordable :)
At 2003.08.24 15:24, you wrote:
The Truth Is Out There
when trying to scroll Dances LisbBox, got exception "Dataset cannot
scroll". I suspect, that KeyLinks & KeySource fields must be set not in
qryDancesLookup, but in the qryClassDancesDet. Am I right, that lookup
dataset is parent?
Thank's for such detailed answer - really helpful. GSG would be great, but
it is not affordable :)
At 2003.08.24 15:24, you wrote:
>3. The dances lookup (for the ClassDances detail query).--/ Gediminas /--
>
>Set up a third query, selecting Dance_ID and Name from table
>Dances. I'll call it qryDancesLookup here. Don't set KeyLinks yet.
>Make Dance_ID invisible. You don't need RequestLive here.
>
>Now we'll take care of the Lookup linkage. This involves three
>steps:
>
> - In the Object Inspector, set qryDancesLookup->KeySource to
> srcClassDancesDet;
> - From the Object Inspector or from within the Query Editor, set
> qryDancesLookup->KeyLinks to: "Dance_ID=Class_Dances.Dance_ID"
> (without the quotes);
> - From the Object Inspector or from within the Query Editor, set
> qryDancesLookup->KeyDescLinks to: "Name=Name" (without the
> quotes);
>
> Attention with the KeyDescLinks: Left of the "=" you put the
> field name from table Dances. Right of the "=" you put the
> corresponding fieldname from qryClassDancesDet. If you have
> implemented this field in qryClassDancesDet with a subselect,
> you should have assigned a fieldname using "AS". This fieldname
> is what you put on the right hand side then.
> But if you have used a JOIN in qryClassDancesDet to get the name
> of the dance, you must qualify the right hand side with the
> joined table name (not its alias I think), so you get KeyDescLinks
> like "Name=Dances.Name"
>
> (Both sides refer to a field from table Dances anyway, but left has
> qryDancesLookup as context, and right qryClassDanceDet.)
The Truth Is Out There