Can anyone explain to me how to do indented portals?

Never having heard the phrase "indented portals" before, I can only guess. If you mean that the first field in the portal is indented for some reason, that can be done (I just did something like that to simulate an XML tree).

First you need a global or calculation field full of spaces (non-breaking spaces are best).

Then a field to specify the "level" of indentation for each portal row/record.

Then a calculation, like:

Field_indented= Left (global_spaces, indentation_level * 5) & field

Put that in the portal instead of the regular field. Make it wide enough.

It can be Unstored if that's fast enough.

Fenton said:

Never having heard the phrase "indented portals" before, I can only guess. If you mean that the first field in the portal is indented for some reason, that can be done (I just did something like that to simulate an XML tree).

Is it possible that this question was about creating NESTED portals? If so, I'd add my question, which is:

If FM lets us use a portal to see all data from a related file, why can't it let us see one of ITS portals? (Surely on some level within the FM application there is an association between the 'portal object' we place on a layout in a master file and the data from the portal's related file?)

Because Portals can be directed to only one file.

You could have a separate portal on the Layout and set the Left key to the ID of one portal row, or use the Value List Items to have a wider view from other related datas.

With some settings, you could have a portal set to a Tree View, involving SelfJoins in the related file and scripting the Left keys of your relationship to have it happen.

But I'm still usure that was what the original poster wanted...