"I cannot create a portal related to the same table as my list" - why not?
Im sorry I worded that wrong. I mean I can not put a portal for my events table on my events layout. Selecting the same table as the one you are viewing is not an option.
You cannot have a portal to the same Table Occurance, but you certainly can to the same Table.
Do you want to see a list of all (or a sub-set of) Events by name on the left say, and when you click on one you see the details of that event on the right? Clicking another one on the list will then show the details of it?
yea that is exactly what i want. How should I relate my table occuraces so that it will show all the records?
Have a Self-Join of Events to Events, using a Cartesian Join (the 'X' - matches everything). That is the basis for a portal that shows every Event. (Though if you're using FM11 or 12 you might want to add a filter to that if the number of events gets too long.)
Create another global field, 'gEventIDToView', as type number.
Create another Self-Join with gEventIDToView = EventID
Using that relationship set the fields on the right side of the form.
Create a script that is:
Set Field [ gEventIDToView ; ThatSecondTableOccurance::EventID ]
Attach that script to the fields in the portal that lists all of the Events. Now when you click on the row you want it will set the global field and display the details of that Event.
You might want to add conditional formatting to the fields of that portal so that if the row's EventID = gEventIDToView then they are filled with yellow, say. That way as you scroll the list you will be alerted to which one you are currently viewing.
If the portal does not refresh cleanly for you as you change the Event selected there are ways to force it to refresh quite nicely.