Re: Filemaker Pro 8 question
Re: Filemaker Pro 8 question
- Subject: Re: Filemaker Pro 8 question
- From: Malcolm Fitzgerald <email@hidden>
- Date: Wed, 13 Sep 2006 16:02:43 +1000
<email@hidden> wrote:
I¹ve not scripted FileMaker 8, but in my experience with versions 4
through
7, embedded AppleScript¹s are already targeting FileMaker by an
implied tell
command. Explicit Œtell application ³FileMaker Pro²¹ and Œend tell¹
commands
are unnecessary and can actually cause problems. Tell blocks ARE
required to
address other apps, such as the Finder, but NOT for FileMaker itself.
This may or many not be the cause of your problem, but it has solved
issues
for me in prior versions of FileMaker. It might be worth a few
minutes time
to see if it helps.
On 13/09/2006, at 1:41 PM, Mara Jade Skywalker wrote:
I've personally found that I got much more predictable results when I
couched the entire script in a 'tell application "Finder"' block,
which of necessity forces me to use the 'tell application
"Filemaker"' block when wanting to talk to FMP.
Don't do that. The best way to get FMP or any app to do what you want
is to deal with the matter in the most simple and direct fashion
(sometimes that's not possible). However, directing all your apple
events through Finder is not good practice.
Think of it this way: Do not wrap everything in 'tell application
"Quark Express"'? That sounds silly, doesn't it?
I've done a lot of applescripting with filemaker. My personal
preference is to have script libraries stored in the application
preferences folder. Load the script library you need at the beginning
of your script and utilise them. Others compile applescript
applications. The most important difference between using script
libraries and using compiled applications is that an application runs
separately from FMP and can control filemaker completely. Scripts run
inside Filemaker, so they cannot do some things, such as access menus.
Both methods work.
Timing issues can be resolved in many ways. Try setting a field value
to something like "Applescript in progress". Have the applescript set
the field to "Applescript complete" when it has finished. Filemaker can
wait until the field contains the correct value. You can do something
similar with a file on disk. Create a file when the jobs starts, delete
it when the job is done: while it exists the job is running.
Malcolm Fitzgerald
T: 0403 972 660 E: email@hidden
Using a Mac? I can automate your workflow with AppleScript
_______________________________________________
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