Re: Timeouts & FileMaker Scripts
Re: Timeouts & FileMaker Scripts
- Subject: Re: Timeouts & FileMaker Scripts
- From: Simon Forster <email@hidden>
- Date: Thu, 4 Nov 2004 11:34:04 +0000
On 3 Nov 2004, at 17:15, Andi Elsasser wrote:
Each AppleScript
opens a *local* FileMaker file that performs an external script in the
multi-
user database being hosted via FileMaker Server. The FileMaker
Scripts, each
one a little different, basically loop through a set of records and
update
other records based on certain criteria.
Andi
I suggest you need to write a control script which checks to see
whether the previous script has terminated before running the next
script. And if your scripts invoke a FileMaker Pro script, can I
suggest you have a trivial call to FileMaker immediately after invoking
the FileMake Pro script? If you invoke a FileMaker Pro script from
AppleScript, control seems to be returned immediately to the
AppleScript (effectively an "ignoring application responses" block).
Frequently this is not what you want as subsequent actions depend on
the FileMaker Pro script doing its thing. I've got into the habit of
calling "modified" immediately after calling a FileMaker Pro script.
Effectively this forces the AppleScript to wait until the FileMaker Pro
script has finished doing its do.
tell application "FileMaker Pro"
activate
tell document theDocument
do script FileMaker script theScript
--Call "modified"
--Forces handler to wait for the database to complete script
modified
end tell
end tell
HTH
Simon Forster
_____________________________________________________
LDML Ltd, 62 Pall Mall, London, SW1Y 5HZ, UK
Tel: +44 (0)70 9230 5244 Fax: +44 (0)70 9230 5247
_____________________________________________________
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden