The auto-enter calc auto-enters when it's first touched. You might want to script this instead. You don't need another table, just another stored field.
agnes b. riley
filemaker and web development
download vCard (http://www.zerobluetech.com/docs/Agnes%20B.%20Riley.vcf.zip)
TWO-TIME MAD DOG AWARD WINNER
FileMaker Certified in 10 and 11 • Member, FileMaker Business Alliance
T: 877 917-9079 . C: 917-660-7221
Store (http://store.zerobluetech.com/) | Blog (http://blog.zerobluetech.com/) | Facebook (http://www.facebook.com/zerobluetech) | Twitter (http://www.twitter.com/zerobluetech) | LinkedIn (http://www.linkedin.com/company/zeroblue-technology-solutions)
1 of 1 people found this helpful
Make sure that the auto-enter calc is dependent on a change occuring in the same table. It won't update based on changes in an unstored calculation alone. Or... when adding a new related SessionParticipant, you could include a SetField step to update the value in Sessions::participantCount
I guess that answers my question. I was hoping the field would update based on the unstored calc updating alone. This isn't something I'm scripting since the registrations are happening on the web using a CWP interface. I was hoping to get it done in schema. I found a way to make it work using just the calc for now. I'll have to explore other options later.
Thanks for the help.
You can still fire a script from the CWP interface, if you like.
How about a plugin? I don't know if ScriptMaster by 360Works server-side, but it may. You can trigger a script from a field calculation box. So, from the Validation calculation of SessionParticipants, you can call a script that updates the parent table.