Please describe the structure of your database. What tables and relationships are involved?
One portal cannot dynamically select different tables or table occurrences as its data source so a different approach will be needed.
I do not think the structure of the database matters. (it is a relational dbase with a patients table that relates to a contact, which in turn relates to a contact type in this case an ECHO)
The nice thing about a portal is, if you are in the layout of the patients table, you can create a portal that looks up/shows the related records from the echo table. But if you are in the echo table, you cannot use the portal to create a lookup of related records from the echo table itself since the portal is created in the layout of the "active" table. Is there a way around this?
I attached a figure where the table of echo is shown, as you can see these records all handle the same patient with different load intervals. I would like to see in my layout which load intervals I already have entered in this table so I cannot make a mistake. Is this possible?
thanks a lot!!
Knowing the basic structure of your database does matter. without a more detailed description of your tables, the purpose of each and how they link in relationships, I cannot make a useful suggestion on how to help you.
Please explain what you mean by an "echo table".
You can create, edit, and delete records though use of a portal so I am not clear why you are encountering problems with your use of a portal, but sharing some more of those design details should clear up that issue for me.