Re: FileMaker 10 - asynchronous commands?
Re: FileMaker 10 - asynchronous commands?
- Subject: Re: FileMaker 10 - asynchronous commands?
- From: Wayne Melrose <email@hidden>
- Date: Tue, 05 Jan 2010 13:44:47 +0100
>>
>
> I found that if you had an AppleScript calling a FileMaker script, FileMaker tended to return control to AppleScript even though the FileMaker script was still running. Frequently this had unfortunate side effects as a next step would rely on the FileMaker script having done its thing.
>
Ahh yes.. "do script" for a filemaker script within applescript within a "perform script" does that, although that's half the reason why I specifically did NOT do a filemaker script within the applescript.
> "Modified" is a FileMaker command which returns a boolean indicating whether the current record has been modified (IIRC). FileMaker will not return a result to this until the (still running) FileMaker script has finished doing its thing. i.e. Its a trivial AppleScript command which forces FileMaker/AppleScript to work in a strictly synchronous fashion. Ugly but then so's AppleScript in many ways.
>
> ;-)
Ahh right, "record modified" would not help in this case ..
>
>> Yeah I guess I could do the search that way, if I was going to do that, I think I'd rebuild the command in FileMaker script, rather than bothering with the applescript equiv.
>>
>> But the thing with this is, it's only happening on, what seems to be the older machine...
>
> Which is why I tend to code defensively when working with AppleScript and FileMaker Pro. I hate it when scripts work fine locally but then have to be debugged on a remote machine with all the latencies that involves.
>
> Usually I develop on my work machine (MacBook Pro running latest OS) for deployment on any old machines running on any old OS - to the point that there's an old box running Mac OS 10.2 in a production setting.
>
> I've got scripts from 2003 that have migrated machine at least twice (and in fact may have started life on Mac OS 8.x). While I'll give full credit to Apple Engineers and the AppleScript guys in particular for allowing seamless transitions through quite serious underlying platform changes, I think my tedious approach to coding has played to these strengths rather than tested them!
>
> ATB
>
> Simon
All good pointes above here, and I agree with the seamless transitions, they've done very well..
I also see your point about the verbos and very GUI approach, I might even look into that more closely.. Still, you'd think this would be more serious issue for FileMaker?
Wayne
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden