portal not populating in join table

[Mountainoak]

I've created a multi-multi relalionship through a join portal. There are 3 tables:

Patient

Patientairway

Airway

The meaning is to select 1 or more airway devices and add them to the patientairway table.

I tried to do this through by making a portal for the airway devices to have a list to pick from. Then using a script to add them to the patientairway portal.

The problem is to get to the portals populated.

Does somebody have a solution for this or an easier way?

Thanks

portal.fp7.zip

[comment]

Try it this way?

portal2.fp7.zip

[Mountainoak]

Thanks this works as i intended but raises an unforeseen issue.

When I try to add a new airway device in the portal of the new TOG this isn't possible as the tick box is shaded in the relationship graph of this new TOG.

Would you be so kind to explain to me why this second TOG needed to be added and how I can modify it to be able add a new airway device in the portal?

[comment]

It's a TO (Table Occurrence), not TOG (Table Occurrence Group). It needed to be added because you wanted to see ALL Airways in a portal. In order to see all Airways in a portal, you need a relationship where all Airways record are related. You could not do this using the existing relationship, where only assigned airways are related.

There are several ways to add new airway records: for example, you could create a script that takes user input into a global field and creates a new record in the Airways table.

If you want to create records automatically by typing directly into the last portal row, you will need to modify the relationship. For example, you could add an unstored calculation field = 1 to the Patients table and a number field to the Airways table, and use these for a relationship using the "=" operator (instead of the current "x").

But I suppose your next step will be to show only unassigned airways in the left portal (do a search for "dwindling"), and if you implement that technique, you won't be able to create records that way once again - so I'd suggest you adopt another method right from the start.

[Mountainoak]

Thanks for the explanation. The option you provided with the unstored field would be enough. I tried but don't get it to work. Would you please help me out one more time. Thanks

portal2_Copy.fp7.zip

Edited March 20, 2008 by Guest

[comment]

Like this?

portal3.fp7.zip

[Mountainoak]

PERFECT