Re: Another FileMaker 7 versus 6 issue...
Re: Another FileMaker 7 versus 6 issue...
- Subject: Re: Another FileMaker 7 versus 6 issue...
- From: Jake Pietrykowski <email@hidden>
- Date: Tue, 18 Jan 2005 09:49:25 -0600
> On 1/17/05 5:32 PM, "David Crowe" <email@hidden> wrote:
> When calling a FileMaker script from AppleScript there used to be an
> easy way to get around the problem of FileMaker returning control to
> AppleScript immediately ... you would just do an innocuous command,
> such as "get version" which wouldn't return until the preceding
> script had completed.
>
> This no longer seems to work in FileMaker 7. I suppose FileMaker is
> now more multi-threaded, so it can handle the "version" request while
> operating the script in parallel.
>
> What is the 'right' way to do this?
>
> - David Crowe
[trying to remember to bottom post]
David,
What is the intensity of your FileMaker script? Have you investigated the
concept of using solely an AppleScript...and kicking the FileMaker script
for this step in your project. Everything that is FileMaker scriptable, can
be AppleScript-ed, with very few exceptions. This would give constant focus
to your AppleScript, and eliminate the 'jumping ahead' when switching
between AppleScript and FileMaker script.
(Post some code, I'll see If I can help.)
I don't know a way, other than telling FileMaker to activate, and then
delay. But a delay may also pause the FileMaker script(not sure), which in
the end achieves nothing.
How long does it take your FileMaker script to execute? What hardware are
you using? Just curious as with these G5's, a LOT of these 'old time' speed
issues have graciously been squashed by the new 'liquid cooled CPUs!' ;-)
Cheers,
Jake
_______________________________________________
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