Re: Running a script library from within Filemaker Pro 6
Re: Running a script library from within Filemaker Pro 6
- Subject: Re: Running a script library from within Filemaker Pro 6
- From: Axel Luttgens <email@hidden>
- Date: Fri, 16 May 2008 23:32:35 +0200
On 16 mai 08, at 22:07, Jim Skibbie wrote:
I have an Applescript that is too long to run inside Filemaker Pro 6’s
ScriptMaker: Perform Applescript command. Apparently there is a 64,000
character limit to the text box you paste the script into in
Filemaker Pro
6.
Almost half of the script is handlers that I could reference by
loading them
as a library (thus allowing me to get below the 64,000 char. limit),
but
from within Filemaker Pro 6, I can’t get this to work. For some
reason I get
the error:
<<script>> doesn’t understand the run message –1708
when Filemaker tries to execute the line “tell library to run” in
the below
script. This script runs fine as a standalone script in
ScriptDebugger, but
not when called from within Filemaker.
Hello Jim,
Usually, the run event is handled by applications or by "real" script
objects.
In your case, library is just defined as a script with a single
handler, "isoDate".
Not sure why you would want to send it a run event, as there isn't
anything to initialize anyway.
So, there are at least two ways to solve your problem:
- either you remove the "tell library to run" statement from the
script in FileMaker
- or you add an empty "on run/end run" handler to your library file
Tested here with FMP 6 on Leopard, both work.
Any thoughts? Is there any way to use osascript from within
Filemaker to get
the library file to run? The main script requires user interaction,
so I
don’t know how much could be run through osascript? When I tried to
run this
from the terminal with:
$ osascript /Users/jim/Desktop/run_test.scpt
/Users/jim/Desktop/run_test.scpt: execution error: No user interaction
allowed. (-1713)
I get an error that user interaction is not allowed?
That's osascript's ambiguity; it is running in a shell-like
environment, which is not a full GUI environment. One is quickly
trying to execute statements expecting more (sometimes unduly) than
what is available in the environment; add to this the lack of
documentation, only experimentation is the way to go.
But, as stated above, osascript shouldn't be needed here.
[...]
HTH,
Axel
_______________________________________________
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