3 to 1

[Ben Ball]

I have a problem.

I have some information by which I am explaining in terms of people.

PLEASE REFER TO THE TABLE ATTACHED.

My Viewing table has 7 fields seperated as

condition X1

condition Y1

condition X2

condition Y2

condition X3

condition Y3

PEOPLE

I am viewing X1,Y1 in a portal

I am viewing X2,Y2 in a portal

I am viewing X3,Y3 in a portal

I have three different people listed in each record as per the above.

Essentially there are all people and really I need to view them in one portal.

How can I do this? Is there a relationship method that will allow me to transfer and view all of these on one portal?

Without having to post them in individually.

Can anyone Help?

3_to_1.zip

[mr_vodka]

Why not display the entire table in one portal and then create a new field in the People table that defines your 'condition'. Then you can use portal filtering to display All the records or show your various conditions.

[Ben Ball]

I may not have been clear in my explaination here.

Your idea sounds good but I need to split the X1,Y1

X2,Y2

X3,Y3.... which are all in the same record....

into seperate lines I suppose this means breaking them into seperate records but this is what I am trying to avoid.

Edited December 19, 2006 by Guest

[mr_vodka]

The basic function of a portal is to be a window per se of related records. My recommendation is to split up the records. Using fields X1,X2,X3 for similar data is just as bad as having tons of repeating fields. Why are you opposed to breaking up the fields into seperate records?

[Ben Ball]

Well I am not opposed as such... I am not sure of an easy way to split the records.

Will this filtering method you suggested enable me to see

X1,Y1 in one line so... I have four records, but in fact I need to show 12 single records in one portal. Can you help with this?

I know what you mean about the repeating fields thing. I just can't avoid this situation.

[mr_vodka]

I was assuming that there was some particular reasoning behind the fact that all those names were split up into individual seperate fields like that. What makes one record and/or field X1,X2,X3 different from the other? If there is a reason behind it, then what I was suggesting was using a field to 'categorize' or rather identify it.

But from what you have posted thus far it just seems as though all those "People" should just be in one table and displayed as seperate records in the portal. So my question to you is why was the database not setup that way in the beginning? What was the purpose of X1,Y1,X2,Y2,X3,Y3 etc?