I'm goign to set up a DB with a 4 part category selection. Part 1 will result in different subcategories in part 2, 2 in 3, and 3 in 4. What would be the best way to do this. Not all the categories go 4 deep, and the last one will have a category number assigned to it.

Thanks

-j

You can do this with value lists. Starting with FMPro 5, hierarchal/conditional value lists are very simple to make. When you set up your value list you tell Filemaker to use values from a relationship. You can use the same concept with portals if you desire.

What I could really use is a way do what your subject says, build a portal inside a portal.

For the portal in a portal idea, Would this work? I haven't had time to try, maybe next week.

Have fields in your file: Category, Sub A, Sub B, Sub C .... etc.

So for instance...

Hammer, Nails

Hammer, Level

Hammer, Level, Pencil

So first portal (category) you select Hammer, based off that Sub A comes up with Nails and Level (Since hammer is on both). Put Level in Sub B and you get pencil. Since no more are left, it get's the corresponding ID #. probably sound easier that it is, ah well. Ideas? Thanks.

I've done this with separate databases, portals and scripts to create a "drill-down" interface. (It's a coin catalogue: country -> collection -> denomination -> date -> variety -> specimen. The ultimate in flexibility it can fit practically any coin from anywhere!)

In the top level database, use a self-join to list all records in a portal (or alternatively use a list view layout). Click on a portal row (or listed record) to go to a layout that shows the record's details plus a portal with all the related records. Click on the portal row to see the related record's details plus a portal with its related records. Click on a portal row to see the related record's details plus a portal... etc for as far down as you want to go.

An interesting interface exercise, to be sure.