I recently moved up from v7 to Advanced v8, and have the latest v8.0.03 update.

-

Try as I may, I cannot seem to reproduce the behaviour that I am

used to when adding a record to the last (vacant) row of a portal

to a related table.

-

Whenever I try to add, I get "This field is not modifiable". I can

add and delete records at will if I use the actual table's layout,

just NEVER through the portal. The relationship is set up to

allow creation of records, but it doesn't seem to work.

-

Help, please !

-

TIA

-

Chris

See if this helps:

http://www.fmforums.com/forum/showtopic.php?tid/193307/

Thanks for that pointer, comment, but that's not the situation

which I have.

-

I have a simple key field in each table which relates the two.

It's just the text character "0". No multiple or complex keying.

-

I have always used "0" as a "catch-all" key to display ALL records

in a related table, which auto-enter "0" as their key as soon as

they are created. This has always worked and now it doesn't.

-

Bit annoying.

-

Chris

Can you post a file showing this problem?

Can you post a file showing this problem?

-

Sure.

-

Chris

test.fp7.zip

I'm afraid you missed the point of the thread I linked to, because that's EXACTLY the situation you have here. This is not about multiple keys - it's about the matchfield on the child side being a calculation field.

Filemaker cannot create children through such relationship, because it cannot set the calculation field to the parent value. This is true for any version, so it has nothing to do with your upgrade.

Thanks for your clear input.

-

The difference between "AutoEnter Data" and "AutoEnter Calculation" is a subtle one, to be sure !

-

It now works fine. I was undoubtedly using my "0" key as data, before,

rather than a calculated field. Just overlooked that.

-

Chris