Apple

On May 10, 2012, at 8:28 AM, Chris Paveglio wrote:

There was a major Applescript execution change that occurred in FM11. It has
do to with executing Applescripts asyncronously now, instead of syncronously
(ie now things can happen out of order, or don't wait for other scripts to
complete their action before the next one fires).
So I would suggest adding in a step between some script commands (in
Applescript not Filemaker script) like:

do shell script "sleep 1"

Even when using FMScripts called from an Ascript, if you call them in order,
you'll get an error that "some other script is executing and request can't
be completed", or something to that effect. In my script, I had to put a
Sleep command after each "show all records" or "clear all finds" steps. Not
sure why those take longer to execute, but the sleep step is pretty much the
"approved" way to handle it now.
Give that a shot and let us know if it works.

Chris

Thanks for your response Chris.

So far, I haven't bumped into that problem yet.

Bruce Robertson posted a fix last noc. The problem was the reference returned from the "create record" step was not recognized by the "go to record" step. Bruce showed how to get the record ID from the returned "create" reference and use that in a "go to record" step. Works perfectly.

I.E. tell application "FileMaker Pro"

set newrec to create new record with data tempDataList at table "AppleScriptLists" of database theDBsName

set newRecID to ID of newrec

end tell

Then use it:

tell application "FileMaker Pro"
go to record ID newRecID
end tell

Joe

References:
	>Re: FileMaker pro changes from v9 to v12 (From: Chris Paveglio <email@hidden>)