Le 3 oct. 2006 à 17:14, David Crowe a écrit : Jay;
You will definitely need a <tell "FileMaker Pro"> block even when running the AppleScript from within FileMaker.
The first thing I'd do is put a display dialog in your try block so you can see what the error is. I doubt that it's related to permissions, because the permissions shouldn't change no matter which application you're running the script from.
I use (path to desktop as string) and then you don't need to cast the concatenated string to type string, but I doubt that this is your problem.
- David Crowe __
Hello
the "offending" handler has NOTHING to do with FileMaker, so it doesn't requires a tell application "FileMaker" instruction.
Simply, as I wrote in my message Objet : Rép : Write file command in Filemaker Date : 3 octobre 2006 16:00:44 HAEC
Re-reading your last messages, I assumes that when launched from FileMaker, your script is unable to know which must execute the write command.
I don't know how one may force it to speak to "Standard Additions" but you may speak to "Finder" or "System Events" coding this way:
It's also what wrote Matt Deatherage ;-)
I was just afraid that the open and close commands available in FileMaker where able to take precedence upon open for access and close access.
Jay Louvion wrote that they doesn't but I don't know exactly the way he implement the "using terms from application instruction.
In the code I numbered 2,every instructions dedicated to the file manipulation are embedded in the using block. In the code numbered 3, only the write is in such a block (and I'm not sure that this one works).
Yvan KOENIG |