Re: FileMaker database access conflict
Re: FileMaker database access conflict
- Subject: Re: FileMaker database access conflict
- From: Simon Forster <email@hidden>
- Date: Thu, 31 May 2012 18:15:22 +0100
On 31 May 2012, at 15:09, David Crowe wrote:
> It is easy to get complete deadlock if you do something like this.
>
> FM Database A: Invoke AppleScript X
>
> AppleScript X: Attempt to access FM Database B
>
> It appears that FM stops dead invoking an applescript.
>
> In one case I solved this by making one of the databases a FileMaker application. This gives it a separate context.
>
> So FM Application A can call an AppleScript that queries FM Database B ... and everything is happy.
IIRC (it's been some time since I scripted FileMaker Pro), this was why we had external AppleScripts living in the same folder as the FileMaker Pro file (or easily referenced from the FileMaker Pro file) which could be called from within FileMaker. You can call this external AppleScript from within FileMaker ignoring application response. Any parameters which need to be sent to the external script could be set in global fields and picked up by the external AppleScript.
Exact details escape me but this sounds about right.
HTH
Simon
_______________________________________________
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