I can get a design where adding data to a Portal in Table1 adds the data to Table2.

However, Table2 requirements are that data once decided upon is more or less meant to be fixed.

Accordingly, this requires creating portal records in a third table where adding data to a Portal in Table1 also adds the data to Table3 (where the data can be modified).

I wonder how to best create a technique in terms of relationship structure for accomplishing this simple task assuming:

Table1_ID (having a portal )

Table2_ID -- item1

Table3_ID -- item1

?

Thanks again in advance:)

No way of doing this through a relationship without a script really... You'll have to make yourself clearer about when the data in Table2 gets "locked" aswell.

Ok -- but I am not sure about the second portion of the comment: I just mean that I need a second set of portal data records -- one set that will be left unchanged and the other that will be available to be changed.

One solution would then be a script to duplicate the data from a set of portal records in table2 to another set of records in table3. Do you have a suggestion on what that type of script would be like?

Perhaps, another solution would be to create a duplicate set of values in each record created by the portal in Table2 which could be modified? In this instance I would skip using table3 as part of a solution.

I wonder is there is yet another solution/design to accomplish my goal?

Any other ideas out there in FM-land?