Re: Finder Network File Copy Timeout
Re: Finder Network File Copy Timeout
- Subject: Re: Finder Network File Copy Timeout
- From: Damon Casey <email@hidden>
- Date: Fri, 4 Jul 2008 11:59:42 +0100
Hi Laine,
Thanks for your explanation. I saved the script as an application and
performed an AppleScript from FileMaker that opens the application and
it all works well. To allow the database to perform the script, I have
to save the application in a FileMaker container field and have a
FileMaker script save the application to the user's desktop, open it,
and put it in the trash afterwards. The AppleScript remains portable
in that I don't have to make sure it is installed on any computer that
uses the database. It's a pain, as in more work, as I would expect the
AppleScript to perform the same whether run from FileMaker or not.
Regards,
Damon
On 3 Jul 2008, at 17:26, Laine Lee wrote:
On 7/3/08 3:55 AM, "Damon Casey" <email@hidden> wrote:
Here's an offhand idea. Turn the script into an application and see
if the same thing happens when you open it in Finder. If the new
app's job is completed successfully, then make FileMaker run a
script that launches the app you just created instead of the
original
script.
--
Laine Lee
Hi Laine,
I ran the FileMaker script yesterday with the Script Debugger active
in FileMaker Pro Advanced and stopped at the Perform AppleScript
script step. I switched to Late Night Software's Script Debugger and
ran the AppleScript from there and the timeout error didn't occur.
I'll now try saving the script as an application and have FileMaker
launch it instead.
My question is, why would the script ignore the with timeout
statement
when being run from within FileMaker but perform correctly when run
in
Script Debugger?
I suspect that FileMaker's scripting implementation wraps around
yours so
that the result is something that might be described as a script
within a
script. The only problem is that while you can modify your script,
you can't
touch the scripting used by FileMaker, it's set at the factory
(although
maybe you can submit a bug report). I apply the same general
perspective to
what happens under certain circumstances when you run a do shell
script. The
way I look at it, you have to break the link between the processes
so that
they can work independently of each other. Technote 2065 describes the
solution of adding "> /dev/null 2>&1 &" to accomplish this for a do
shell
script, I just made the same sort of suggestion for your FileMaker
situation.
I'm not the best at explaining, and I may have just made a lucky
guess. The
real cause may not have anything to do with what I'm talking about.
Anybody
can hit one out of 50.
--
Laine Lee
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (applescript-
email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden
_______________________________________________
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