Hi Bruce,
I'll give it a try.
Thanks,
Chuck
On Feb 20, 2009, at 9:44 PM, Bruce Herbach wrote:
Hi Chuck,
If you need to commit the change and then exit the field, try
this. Give something other then a field an Object name. Then have
your script commit the record then perform a Go To Object script
using the named object. This should both commit your record and
leave the field/record.
Hope this helps
Bruce Herbach
Chuck Pelto wrote:
Greetings All,
Earlier I had complained that the Go to Field function in
ScriptMaker no longer exited a record if the parameter of field to
be gone to was left blank. It worked in FMP6 and in FMP9, but it no
longer works in FMP10.
I've discovered that the 'Commit' function is supposed to do that.
Well....guess what.....it doesn't.
Here's the description of Commit from FMP Help.
Description This script step exits the current record or find
request <http://fmhelp.filemaker.com/fmphelp_10/en/html/glossary.html#1027732
>, updating field data and making no field active.
So I have this call in a ScriptMaker script that is triggered when
the user changes a field using the new Script Triggers
functionality. The Commit function is there to exit the record so
that relationships can be updated and records in other tables are
adjusted to reflect the change. BUT Commit, in this situation,
doesn't exit the record where the field was changed. Therefore I
have to manually click in some blank area of the layout in order to
get it to exit the record and allow updates to occur.
If I run MY script with Commit in it and THEN run another script,
manually—from the run button in , with the Commit function in it,
the Manage Scripts window, it DOES 'commit' and relationships and
data in other tables are updated.
It looks to me like there is a flaw in the Script Trigger
functionality that causes Commit to not play well.
Is there a work-around? Who do I take this problem too?
Regards,
Chuck
