When you have fields in a portal they must all be based on exactly the same TO (or 'relationship') that the portal itself is based on. (Not absolutely true; you can have down-stream fields, but for this case I suspect this is one of your problems.) Double-click the portal and check the relationship name at the top. Double-click each field in the portal and make sure the relationships are exactly the same as the portal's.
Yes, the portal is based on DUES as is each of the fields on the portal.
The perlexing part of this for me is that Dues::Setup_Total will NOT display when placed on the portal (based on dues) but it does display correctly when on the SETUP layout which is also basedon DUES? What is that about?
I had this thought. What about making alll the above fields global and then scripting global bariables (like $$total= Global::setup_total) then using SetField to bring the $$total into the correct field. When the global variables change, I don't think the assigned field value will change.
It i 2:20 am and I am off to bed... Your thoughts are appreciated.
You are confusing me: I can't work out which field(s) and portals you mean. These second two seem to me like you are putting (can I say 'copying and pasting'?) the same field into the same portal on both occasions:
Dues::Setup_total works when placed on the SETUP layout (based on DUES).
But, if I take the same field (Dues::Setup_total) and place it on the Dues based portal on the Members layout it comes up blank?
If I put Setup_Total on the same portal, IT WORKS
Can you confirm what the relationship is between the two tables, by the way?
I still think that you are not attaching the same relationship to the fields and their portal. If you draw a new portal and follow the wizard, adding the field Dues::Setup_total only from the list of fields it offers you, how does it appear then?