Re: Filemaker 8.5 stored applescript problem
Re: Filemaker 8.5 stored applescript problem
- Subject: Re: Filemaker 8.5 stored applescript problem
- From: Shane Stanley <email@hidden>
- Date: Thu, 17 May 2007 20:44:10 +1000
- Thread-topic: Filemaker 8.5 stored applescript problem
On 17/5/07 6:22 PM, "David Simerly" <email@hidden> wrote:
> Granted, there is a problem executing Standard Additions read/write commands
> from a ScriptMaker ³Perform AppleScript² step, but it¹s not a terminology
> conflict.
It is precisely a terminology conflict. The English term "read" has a
meaning defined in FileMaker's dictionary, and it conflicts with, and
overrides, the terminology used by Standard Additions' read command.
If you compile the script in Script Debugger using FileMaker as target and
showing the codes, you'll see exactly what happens -- the word "read" gets
turned into the code used for the read enumeration in FileMaker.
> As an example, look at the ³everyones privileges² property of the Finder¹s
> ³item² class; it also has read/write constants
No it doesn't; it uses "read only" and "write only", which are quite
different.
--
Shane Stanley <email@hidden>
AppleScript Pro Denver, June 2007 <http://scriptingmatters.com/aspro>
_______________________________________________
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