Do you have any privilege sets defined for this database? Performing a script with limited privileges can result in errors that do not occur when debugging with Admin access. Double-check the context. I've encountered privilege set restrictions a number of times and it can be a nuisance to get them sorted.
Are your scripts behaving differently on FMP10A compared to an earlier version?
Thanks for the reply. The scripts run with full privileges. There are no other sets defined. Oddly enough, if I run it for a second time, it works! Running it from a backup copy also works.
Thank you for your post.
It's difficult to determine what may be the problem. Besides using the Debug mode, try inserting a "Halt Script" script step in a strategic place to make sure fields/variables/etc. are being updated properly when the script is run. If it isn't, and it does work in Debug mode, then the script may be somehow corrupt. (I don't know why that would occur). See if you can determine where the breakdown occurs.
Try creating a new script, or a sub-scripts and call that from the main script. See if that works correctly.
Sorry I can't be more definite without seeing the script.
I inserted a .5 second pause after a Commit step and it works fine. This would seem to add 10 seconds to a payroll of twenty people, but in effect doesn't lengthen the entire process at all since the refresh time is now spread out over however many records are being processed. I'll also try it with a shorter pause.
Do you use a "do script" in your code?
If so, you should know that there's been a known bug in v11 for OVER A YEAR where a "do script" returns control to the AppleScript Interpreter BEFORE it's completed. This tends to cause all sorts of problems which may or may not occur due to realtime constraints.