Relationship to act as a filter

[HunterBoss]

This is the first time I've done an attachment, so I hope I've done it right.

I thought this should be easy, but I can't seem to figure out what I've done wrong.

I have a customer table.

I also have a resources table.

The resources table has a Customer Type field that's saved as a global. Its value comes from a value list.

The customer table has a similar Customer Type field. Its value comes from the same value list.

I can set the customer type in the resources table.

I want a layout that shows customers whose customer type is that set in the resources table.

I would have thought a table occurrence and a simple join with the resources table would have accomplished that, but it didn't.

Yes, I've checked many times. My layout is based on the correct table.

Help.

Thanks in advance.

Christopher

Edited March 3, 2008 by Guest
typo

[Søren Dyhr]

Why do you have customers in both tables? If a match or more exists will those line up in the portal shown in Resouces.

--sd

[HunterBoss]

SD

I've added the test file I'm using to try out my ideas. the only difference between this and what I tried yesterday was that I've added a numeric field to both tables to see if that worked. it didn't.

The customers are not in each table.

The customer type is.

I was hoping to use this type of relational link between 2 tables to act as a filter or found for the full list of customers.

in z_Resources I've entered a "1" as the value in the link field.

in the customer table I've created a link field as well and set some of them to "1" and some of them to "2." With how I have the relationship set up between z_Resources and CUSTOMER_plantype_yearend, I would have expected only customers with a "1" entered in their link value to show up in the layout view for CUSTOMER_plantype_yearend.

What, pray tell, am I missing?

thanks

Christopher

(ok, I see that one of the hot topics is a self-joined filtered layout, so I'm trying to do something that should be doable.)

Test_Tables.fp7.zip

Edited March 3, 2008 by Guest

[comment]

I think you have a misunderstanding here. Layouts are not filtered by relationships. Only portals are.

You can get any layout to show any or all records from the underlying base table - regardless of which table occurrence is the layout based upon. It's purely a question of finding/omitting (including finding by GTRR, which uses a relationship to make related records found).

To see only those child records that are related to the current parent record, place a portal to the child table on a layout of parent.

[HunterBoss]

thanks

just went and tried it

I knew it was going to be easy if I did it right. :

without doing a find or a portal, there's now way to limit the records that can be seen within a specific layout?

Christopher

[comment]

There is no way to limit the records that CAN be seen within a specific layout, period. A find merely creates a temporary found set. At any time, user can change the found set by performing another find, including Show All Records (if user has privileges to do so).