Geoff, Steve, and John:
In my original database relationship Table_Jobspecs (MarComProjects)
is related to Parts via ProjNum=ProjNum_job AND
Constant=Constant_Job. I duplicated the same relationship and swapped
Constant and Constant_job with Mail and Mail_job naively thinking
this would work and changed the name (since you can't have two named
the same) to Mail. This maybe where I went wrong.
Comments?
Also if I un-index the fields Mail and Mail_job nothing shows up.
Peter
On Oct 8, 2009, at 8:37 AM, Geoff Graham wrote:
On Oct 7, 2009, at 4:51 PM, Steve Cassidy wrote:
...
But then I've now had a further glass of wine. I could be wrong.
...
One more glass Steve and you may attain true clarity.
Peter,
The line from the starting table occurrence (the layout) to the
destination table occurrence (portal content) is not what your
portal wants it to be. Now if you're sure the portal is set right,
that leaves your relationship graph. It's one of the two right? You
ruled out calculations evaluating from the wrong context.
I'd start troubleshooting by placing another (temporary) table
occurrence in the graph that is what I think it should be, then
bring a related field into an unused area of the parent's layout.
I'd expect to see the first related child record's data. Then a
simple 6 line portal over that. A serial field or some other
identifiable data from the related records would be my choice. Kind
of a take it from the top approach.
I've certainly fought this one before.
Geoff
