Portal weirdness, or is it me?

[Pat]

I created a layout with portals from relationships with two criteria (ClientID and SlotUsed, between Client table and Prescription table). Works great. Needed the same layout involving another table (Client table and OTC table), so I did for it what I did for the other. I have checked the variables, the relationships, the layout, and everything matches. Except, nothing in these new portals show on OTC layout. You can't even click into the fields (yes, I have browse checked in the behavior). I duplicated the layout, changed the portal to the corresponding OTC verison, the variables to the corresponding OTC version.

Prescription layout

Layout based on:

Client table

Portal based on:

Cli__prescription~ClientID and SlotOneUsed

ClientID in CLI = fkClientID in prescriptions

and SlotOneUsed in CLI = SlotOneUsed in prescriptions

OTC layout

Layout based on:

Client table

Portal based on relationship:

Cli__OTC~ClientID and SlotOneOTCUsed

ClientID in Cli = fkClientID in OTC

SlotOneOTC in cli = SlotOntOTC in OTC

Anyone have a clue why what worked in one case doesn't work in the other? Thanks for the help.

[LaRetta]

You haven't mentioned whether you have verified that the fields within the portal are referencing the same table as the portal. This might explain inability to access the fields. But you mention variables and I assume you mean globals because variables can't be used in relationships. It might be difficult to pinpoint. But you can try these:

1) Place the related fields directly on the layout (and don't use the ones from the portal; reselect them again from Insert > field. Anything show up? Do you have related records? Do the keys match?

2) Do you have Field Control > Behavior checked to allow entry in Browse into the fields in the portal?

3) Where is the global? In this instance, is it on the child side (portal side)? If so, your relationship won't work.

4) Re-check relationship specified in Layout, Portal and Fields. They are named very similarly; it's bitten me in the past as well.

5) If still no luck, maybe give us a view of these relationships in your graph. Sometimes we can spot errors such as data not flowing the direction you require.

6) Reminder again - check Layouts > Layout Setup and verify which table it is based upon and make sure it is your Client table.

If none of these things help you, we will probably need to see your file. :wink2:

Edited February 26, 2008 by Guest
Added 6

[Pat]

You haven't mentioned whether you have verified that the fields within the portal are referencing the same table as the portal [color:red](yes, checked this and they are). This might explain inability to access the fields. But you mention variables and I assume you mean globals because variables can't be used in relationships.[color:red](My bad, I mean fields, neither of which is a global-text to text and number to number) It might be difficult to pinpoint. But you can try these:

1) Place the related fields directly on the layout (and don't use the ones from the portal; reselect them again from Insert > field. Anything show up? Do you have related records? Do the keys match? [color:red]Did that, nothing showed up, and yes the keys match, there are records.

2) Do you have Field Control > Behavior checked to allow entry in Browse into the fields in the portal? [color:red]yes

3) Where is the global? In this instance, is it on the child side (portal side)? If so, your relationship won't work. [color:red]no global, but something I didn't know! :

4) Re-check relationship specified in Layout, Portal and Fields. They are named very similarly; it's bitten me in the past as well. [color:red]Have done this more than once! I'm used to doing silly things, so I do check for those!

5) If still no luck, maybe give us a view of these relationships in your graph. Sometimes we can spot errors such as data not flowing the direction you require. [color:red]I'll check this again, but I think I've checked it.

6) Reminder again - check Layouts > Layout Setup and verify which table it is based upon and make sure it is your Client table.

If none of these things help you, we will probably need to see your file.

Thanks for your suggestions. I'll let you know if anything changes. I put it away for two days hoping I would get wise with the time away, unfortunately that didn't happen!

[LaRetta]

"I put it away for two days hoping I would get wise with the time away,"

LOL, I've tried a month and it didn't help. Not to worry, we'll be here. And one way or the other we'll figure out what's going on here. Hang in there, Pat. :smile2:

[Pat]

I took snapshots of the relationship edit box for the prescription and OTC relationships, a snapshot of the relationship graph, and a snapshot each of the portals. Hope this helps someone clue into something!

Relationship1.pdf

Relationship_2.pdf

Realationship_Graph.pdf

Rxportal.pdf

OTC_portal.pdf

[Søren Dyhr]

Attachment: Realationship_Graph.pdf (41.1 KB) 5 View(s) [Download]

We have honestly all made the same kind of relational approach, only to learn we have made it way to difficult for both the machine and ourselves. What you probably have is type mismatch in some of the keys, but I would suggest you ditch the used approach, and instead make the relational approach this way:

http://www.fmforums.com/forum/showpost.php?post/205259/

...there are two approaches in the same template, but I suggest the one with the global, and a fixed number of sandwiched records.

--sd

[Pat]

Thanks! I am in the process of digesting the file and applying it to my situation. I find if there is a harder way, more complex way, that's what I usually come up with. Which makes this forum so amazing and helpful for people like me!

[Søren Dyhr]

I find if there is a harder way, more complex way, that's what I usually come up with

Thats what we all tend to do! Nothing to worry about there, you'll get there with enough effort and dedication - I promise!

--sd