Re: Relationship for portal based on valuelist

"A.J." <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
>
> Glenn Schwandt wrote:
>
> > "A.J." <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]
> > > Hi
> > >
> > > My question is...
> > >
> > > Is it possible to ha a valuelist to decide which relationship to be
used
> > > in a portal?
> > >
> > > f.ex
> > >
> > > When I select "A" from a valuelist. I want to use relationship "1" in
> > > the portal. When I select "B" from
> > > the same valuelist I want relationship "2" to be used for the same
> > > portal, and so on.
> > >
> > >
> > > A.J.
> > >
> >
> > Base your single relationship on a calculation field something like
this:
> >
> > LeftSideKey (calculation, number) = Case (Selection = "A", 1, Selection
=
> > "B", 2, Selection = "C", 3, 4)
> >
> > You can substitute whatever is required for the numbers above (like
field
> > values or complex calculations) to influence which records are related.
>
> I´m having a problem doing it the way you describe. What happens is that
when
>
> I modifi the relationship, I get the rerror that the calculated field
cannot
> be indexed.
>
> Any ideas?
>

That sounds like you are trying to create a calculated "Right Side Key" (as
viewed in the relationship definition dialog)...I suggested the calculation
for the left side.