Tim Harris Posted March 19, 2008 Share Posted March 19, 2008 I'm trying to create a portal that displays data from a relationship that has a unstored calculating field on the left had site. On the layout I have the portal, and the calculated field. i can see the calculated field change as I change another field (and click in the calculated field box), but the data in the portal does not change. When I change the relationship to a field that is normal indexed it is fine. I see posts about it being OK to have unstored field on the left hand side, so it must be something silly that I'm doing. Link to comment Share on other sites More sharing options...
Ender Posted March 19, 2008 Share Posted March 19, 2008 The left-hand, right-hand meanings are not so clear in this age of relationship graphs, where the relative positions of the TOs don't matter. Basically, you can have unstored calcs as parent keys, but not as child (foreign) keys. In this context, think of the parent keys as fields in the current layout's table, and child keys as fields in related tables. Link to comment Share on other sites More sharing options...
Tim Harris Posted March 19, 2008 Author Share Posted March 19, 2008 Thanks.. I can confirm that that is how I have it. My parent key is calculated and in the current layout. The child key is in another table from another file in fact. The calculated parent key is one of a small number of possibilities and when displayed on the screen I can see it change. The data is the portal is loaded is seems from the first time the parent key is calculated but never thereafter once it changes. Link to comment Share on other sites More sharing options...
Ender Posted March 19, 2008 Share Posted March 19, 2008 It sounds like we would need to see more details about how the parent key and child key is defined. Link to comment Share on other sites More sharing options...
Tim Harris Posted March 19, 2008 Author Share Posted March 19, 2008 Does this help (I hate these reports) http://www.clayford.com/fmpproblem/summary.html Look at mangofinance, table VAT. The field VAT_CompanyTabName is what I think is the Parent of the relationship. You can see that in relates to table VAT|Ledger:Ledger_Business. Link to comment Share on other sites More sharing options...
AHunter3 Posted March 19, 2008 Share Posted March 19, 2008 I have had this problem fairly often when the parent-side ("left hand side") key field is an unstored calculated value. Portals don't always "wake up" and refresh properly. A quick Enter Find Mode [no pause], Enter Browse Mode can kick it, as can Refresh Screen [flush cached join whatsits], as can go to previous / go to next record; sometimes one such technique will work where the others do not (the Refresh Screen is probably the one to try first). I've found it to be particularly a problem where the actual table in which the unstored calc field resides is not actually in the current file, i.e., the table occurrence native to the current layout is of an external file's table. See it annoyingly often in systems where data & structure have been separated. Link to comment Share on other sites More sharing options...
Tim Harris Posted March 19, 2008 Author Share Posted March 19, 2008 not sure it is that on this occasion. Something more basic I'm sure, but cannot see it myself. Link to comment Share on other sites More sharing options...
Ender Posted March 20, 2008 Share Posted March 20, 2008 Sorry Tim, I'm not visualizing it. I'd probably need to actually poke around in the file (or an example file with the same relationship setup) to understand what's going on. Link to comment Share on other sites More sharing options...
By Soliant Consulting,
By Soliant Consulting,
By Soliant Consulting,
Recommended Posts