Cascading portals - limiting results based on active field in another portal?

[Ray-El]

I'm trying to come up with a way to allow users to create a list of cascading categories, which will eventually be used to help customers narrow down products on a website.

The first two categories are entered for them in two fields in the same table. So they would see the following listed:

Record 1: Garage Tools

Record 2: Kitchen Silverware

When they click on the record 1 ( Garage - Tools), a portal shows them all the subcategories for that record and allows them to add more as needed, such as:

Hammers

Drills

Saws

Crow Bars

I added a second portal so that when they click on any of the subcategory records in the first portal, the second will show them only the records from a third table related to the ID of the record selected in the second portal.

So you click on "Garage - Tools" and see "Hammers" in a portal and can then click on the "Hammers" record in the portal and you see types of hammers listed in a second portal.

For the most part, it's working, except for the second portal. No matter what record I click in the first portal, the second portal will only show the records related to the first record listed in the first portal.

So, using the example above, you click on "Hammers" and see the types of hammers listed on the second portal. But if you click on "Drills," you still only see the records related to hammers in the second portal.

Is there a way to get a second portal to display only records related to the ACTIVE record of the first portal? I plan to add a 3rd portal, too.

Thanks for any suggestions.

[qube99]

Maybe this will give you some ideas...

http://fmforums.com/forum/topic/72391-getting-more-out-of-filtered-portals-6-hierarchical-portal/

[Ray-El]

Thank you for the tip. Very nice sample. I'll have to dissect it and see if I can understand what's driving it.