Portal within a Portal

[edmonton]

Hi

Here is the scenario

I have three tables

Client

ClientDepartment

ClientDeptContact

Client to ClientDept is one to many relationship

ClientDept to ClientDeptContact is one to many.

In Client Layout, I would like to show a portal with departments and contacts in that department....

One Client will have many departments and each depts can have many contacts....

How can I do this :

[Deep Thought II]

i dont think u can do this, i tried many times before as well, but the portal within the portal shows only the first record and does not expand by itself.

i sort of used a small button on each portal row to allow opening a new window showing the information on the second portal that i want to show...

there may be other ways around, too.

[edgaroso]

hello:

i was wondering if you could give me the script you are using for placing a small button on each portal row in order to open a new window showing specific portal row information in a second portal?

i have a portal referencing many photographs (containers) which is working fine. but i have no way to have the user to click on a specific photo in portal 1 and jump to information on that specific photograph. i think the button thing you're doing would be my solution - at least i hope it is!

thanks in advance!

edgaroso

[transpower]

Access can do that; FM cannot. Try popping up another window.

[hayesk]

transpower, maybe I'm misunderstanding edgaroso, but why couldn't FM do what edgaroso describes?

Place the button in FM to launch a script. The script opens the window with a layout containing the photograph information. I'm not seeing why there are two portals in his case.

As for the original poster, you can have two portals side by side. Clicking in one portal can run a script to set a field that satisfies the relationship in the second portal.

[Chuck]

You can also do this on a single window, if you prefer, which may be the case as you were wondering about a portal within a portal.

Create a global field in ClientDepartment that is of the same type as that table's primary key. Assuming that you have a table occurrence called Client and this is related to a table occurrence called ClientDepartment via a ClientID field, create a relationship from ClientDepartment to ClientDeptContact with gClientDepartmentID as the match field in ClientDepartment and ClientDepartmentID as the match field in ClientDeptContact.

Here's a pseudo representation of the relationship diagram:

[Client]<ClientID>-<ClientID>[ClientDepartment]<gClientDepartmentID>-<ClientDepartmentID>[ClientDeptContact]

Place a button on the portal into ClientDepartment that has the following step:

SetField[ ClientDepartment::gClientDepartmentiD, ClientDepartment::ClientDepartmentID ]

Place a portal into ClientDeptContact on the same layout. When you click a Department, the related Contacts will show up in the second portal.

Another alternative: use a list view on a layout that is attached to ClientDeparment. Place all Client specific information in the header, place ClientDepartment information in the body and a portal to ClientDeptContact also in the body.

Chuck

[transpower]

I like that--just have two portals side-by-side.