Re: Persistence of properties in AppleScripts within FileMaker Pro scripts
Re: Persistence of properties in AppleScripts within FileMaker Pro scripts
- Subject: Re: Persistence of properties in AppleScripts within FileMaker Pro scripts
- From: julifos <email@hidden>
- Date: Tue, 04 Mar 2003 17:05:10 +0100
>
I'm trying to set up some tools of convenience for myself in a
>
FileMaker Pro database I made that tracks my students' marks, lab
>
attendance, etc. I've attached several FileMaker Pro scripts to
>
buttons and part of the FileMaker Pro script is often an embedded
>
AppleScript. The current script I want to use in this way requires me
>
to store a property, but there seems to be no persistence of
>
AppleScript properties between runs. I can't think of a workaround in
>
AppleScript. I could, of course, make a field in the database and
>
store it there, but I would rather not - it's already got 250 fields.
>
I guess one more wouldn't hurt, but...
>
>
Does anyone know how to make properties stick in AppleScripts run
>
within FileMaker Pro's scripting architecture?
>
>
- web
I'm not a FM expert, but seems that FM executes a text script, anything such
as a "do script" command or:
run script "set x to x +1"
So, if no compilation, not properties persistence... Sweet ways are your
idea about create a new field (if you can store such property in a text
field), write it to a preferences file, or directly execute the script from
an external compiled script, or store the results into one:
Perform AppleScript ["run script alias 'path:to:script'"]
Perform AppleScript ["store script x in file y replacing yes"] (which is the
same as write the property to a file)
JJ
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.