child through portal: need explanation please

[aswi]

Hi,

I have figured out what needed to be changed in order for the following to work, but I don't understand why. I'm hoping someone can explain it to me.

I have two tables: Insurance and Client. I need to be able to see all Insurance companies available in all the Client records. I also have to be able to add new insurance companies to the list while I'm in a client record because the one that is needed might not be in there.

So the relationship that was set up was Insurance::onelink (where onelink was a *stored* calculation equal to 1) to Client::linkis1 (where linkis1 is a global auto-entered validated number equal to 1). Adding of record through relationship on Insurance side was enabled. (Obviously the all to all realtionship type (x) was not going to work because I had to be able to add through it.)

But this relationship did not allow me to create a new Insurance record throuhg the portal.

When I changed the Insurance::onecalc field to also be a global auto-enterd validated number (equal to 1) then the problem was solved.

I understand that you can't create relationships on unstored calculations but this was specifically a *stored* calculation. WHy did it not work the original way?

Thanks.

[Razumovsky]

Hi there-

My understanding is that FileMaker creates new records through portals by entering a matching value into the relational key field in the new record in the related table. Calculation fields (be they stored or unstored) only display calculated results and do not accept input. Therefore, FileMaker can not create new related records through a relationship where the child key does not accept input.

Also, note that because you are using Global fields on both sides of the relationship (which still makes me nervous), you will not need to auto enter a 1 for each new record as all records will share the same value (definition of a global).