As far as I understand IBO ideology, in this case it is necessary to
use 4 instances of "CLASSES" dataset. One dataset per each tib_lookupcombo.

It as relational structure ideology. 4 instances of lookup table joins
to main table:

select
S.LastName,
(select ClassCaption from CLASSES where ClassID=S.Class1ID),
(select ClassCaption from CLASSES where ClassID=S.Class2ID),
(select ClassCaption from CLASSES where ClassID=S.Class3ID),
(select ClassCaption from CLASSES where ClassID=S.Class4ID)
from STUDENT S

or like this:
select
S.LastName,
C1.ClassCaption,
C2.ClassCaption,
C3.ClassCaption,
C4.ClassCaption
from
STUDENT S
join CLASSES Ñ1 on C1.ClassID=S.Class1ID
join CLASSES Ñ2 on C2.ClassID=S.Class2ID
join CLASSES Ñ3 on C3.ClassID=S.Class3ID
join CLASSES Ñ4 on C4.ClassID=S.Class4ID

but not like this
select
LastName,
ClassCaption where C.ClassID=S.Class1ID,
ClassCaption where C.ClassID=S.Class2ID,
ClassCaption where C.ClassID=S.Class3ID,
ClassCaption where C.ClassID=S.Class4ID
from
STUDENT S, CLASSES

--
Best regards,
Ramil R. Khabibullin khabibr@...

>
>
>
>
>
> I have an application where I need to keep track of CLASSES what
> STUDENTs wish to sign up for in different quarters of the school
> year. I have a table that stores all available CLASSES. I have a
> form that has several tib_lookupcombos. In the BDE version, since
> the lookupcombo has both a list source/keyfield and a
> datasource/datafield relationship, I can have all of the
> lookupcombos accessing the same "CLASSES" table yet updating
> different fields in the STUDENT file so the STUDENT can sign up for
> 4 different CLASSES, 1 per school quarter. In the IBO version I
> can't figure out how to accomplish the same thing. Since the
> tib_lookupcombo only has a datasource and, as far as I can figure,
> the relationship is set using keylinks, am I limited to one
> tib_lookupcombo on the form since adding more continue to update the
> same field in the STUDENTs file based on the defined keylinks. I
> realize that I can keep changing the keylinks but that only semi
> works because it messes up the display since once changed the
> tib_lookupcombo that displayed class x now displays class y because
> the keylink effects all of tib_lookupcombos on the form. Can
> someone tell me what I am missing?
>
> Thanks
>
>
>
>
>

--
Best regards,
Ramil R. Khabibullin khabibr@...

>
>
>
>
>
> I have an application where I need to keep track of classes what
> students wish to sign up for in different quarters of the school
> year. I have a table that stores all available classes. I have a
> form that has several tib_lookupcombos. In the BDE version, since
> the lookupcombo has both a list source/keyfield and a
> datasource/datafield relationship, I can have all of the
> lookupcombos accessing the same "classes" table yet updating
> different fields in the student file so the student can sign up for
> 4 different classes, 1 per school quarter. In the IBO version I
> can't figure out how to accomplish the same thing. Since the
> tib_lookupcombo only has a datasource and, as far as I can figure,
> the relationship is set using keylinks, am I limited to one
> tib_lookupcombo on the form since adding more continue to update the
> same field in the students file based on the defined keylinks. I
> realize that I can keep changing the keylinks but that only semi
> works because it messes up the display since once changed the
> tib_lookupcombo that displayed class x now displays class y because
> the keylink effects all of tib_lookupcombos on the form. Can
> someone tell me what I am missing?
>
> Thanks
>