Hi Comment,

Your input is ALWAYS invaluable...

I'm on a Layout entitled PROJECTS, on which I wish to include a set of tabs which displays projects according to status (eg, Active, In Development, Cancelled).

I'd like each "tab" so to speak to display a portal of projects of like status (eg, a portal showing only Projects which are "Active" on one tab, and Project which are "In Development" on another tab).

I set up a calculation field in the PROJECTS table for each Status value (ie, "Active", etc). I then related each calc field to the Status field in the same table. I then created a PROJECTS layout for each Status portal to show records from the appropriate self-join relationship. But instead, they each show ALL of the records!

Can't seem to get around it. I relied on self-joined relationships heavily in the old version of FM Pro. Either I'm a bit dusty, or it works differently. Can you help?

Thanks!

J

Edited September 18, 200817 yr by Guest

See here for another way.

http://fmforums.com/forum/showpost.php?post/289032/

But if you are creating 3 seperate table occurrence joined on each calc field to the status field, as long as your portal reflect those relationships, it should work.

BTW I split this topic into its own thread.

Edited September 18, 200817 yr by Guest

I agree with John (I think - I don't understand that file all too well). In a nutshell, you only need one relationship, based on matching a global gStatus field with the "real" Status field. Make yourself 3 buttons, each setting the global to a different value, and use them as fake tabs.

Lol. Sorry I should have opened that file. That was a modified file of that thread's OP. My point was that tabs are a layout presentation tool, not a native filtering tool. :-)

You cleared up my mess nicely.

Hmmm...

Same problem! I created a gStatus field, and a script which sets that field accordingly (ie, "Active").

I then created a self-join relationship between gStatus and ProjectStatus.

I then created a portal on a Projects layout; the portal shows records from the self-join relationship.

But the portal shows all of the records, and not just the ones with the matching status.

Can you help? Thanks!

J

My guess would be that you have things the wrong way around. If your layout is based on the Projects TO, and you have a self-join relationship to Projects 2, the relationship needs to be:

Projects::gStatus = Projects 2::ProjectStatus

and the portal needs to show records from Projects 2.

That nailed it; didn't know the order of setting up the relationship mattered, lol. Thanks for that, Comment, you're awesome : )

It's not the order, only the global cannot be on the child (portal) side, because Filemaker needs to index the matchfield there.