OK Filemaker buddies.

This has to be basic [read a stupid question] but it still confuses me

Hi,

Not sure I followed your file structure.

EventMaster.fp5

Recipes.fp5

EventItems.fp5

The Portal in EventMaster.fp5 related to the EventItems.fp5, but you said this EventItems.fp5 currently has only 2 fields

event_key [to tie back to EVENT_MASTER] and recicpe_uniquekey [to store what recipes that event will be using]

So you won't be able to have a RecipeName in the portal unless this field is in the EventItems.fp5.

Another approach would be to create a Value List in the EventMaster.fp5 file. Choose Value from File and pick up the Recipe_Key for first key, and Recipe_Name as a second value. Sort this VL by the second field, and you'll be displayed with either the Id and the Name of that Recipe.

You would still need a Recipe Name in the EventItems. Create that field there, and define it to be a lookup field from relationship EventItems.fp5::Recipe_Id::Recipes.fp5:Recipe_Id.

Only in the portal in the EVENT_MASTER record I need to give the user a PopUpp menu of recipe NAMES [so they don

I am too tired now to even think of my original question. But I think you may have clarified an important piece. For a field to be shown in a portal is HAS to be in THAT file [the related file]. So to have the recipe_NAME I would have to have a field that COPIES [via Lookup] the text value for the recipe_NAME in the EventItems.fp5. I was trying to see if I could keep it normallized. The EVENT-ID field structuraly would seem to need ONLY a Recipe_Key and an event_key to tie it back to the EVENT_MASTER.fp5 file. But, the user obviously wants to see what the recipies are. I was hoping to be able to place a related field [related to the internal portal datase] to show that value. But it seems I must copy it via a Lookup and have the name field in the portaled file. Am I correct here? And thanks for all your help.

-- Eric Zork Alan

-- author:

Hi Eric,

You can put all of this stuff on your bio page, and then not have to put it in every post.

[color:"blue"] > -- Eric Zork Alan

> -- author: