This topic is 1803 days old. Please don't post here. Open a new topic instead.
Hello, I have a database that I run on 3 different computers, all with Mac OS 11.2. FMpro is 184.108.40.2067.
A script uses an AppleScript that opens a browser. The AppleScript invokes System Events and contains a "do shell script" step.
On all computers, FMPro, Script Editor Script Menu are "allowed to control computer" in System Prefs.
In the other 2 computes, with the Intel chips, the script runs flawlessly but it stumbles on the M1. M1 vs Intel is the only difference between there 3 setups. I know that v18 is not officially supported with Big Sur but the programs runs perfectly well. Any suggestions would be appreciated.
Hello, the following is the essence of a problem I need to resolve. The code is AppleScript
display dialog "Hello \"world\" " This code needs to run in FMP18 as a calculated applescript.
Perform AppleScript [display dialog \"Hello "world" \"]
Perform AppleScript [display dialog \"Hello \""world"\" \"]
Perform AppleScript [display dialog \"Hello "\"world"\" \"]
Perform AppleScript [display dialog \"Hello \""world\"" \"]
and other permutations of 1 backslash and 2 quotation marks cause the calculation to be unsavable b/o error.
Perform AppleScript [display dialog \"Hello \"world\" \"] results in "A identifier can’t go after this “"”." -- after the calculation is saved. (Yes, "A identifier")
Perform AppleScript [display dialog \"Hello \"\"world\"\" \"] results in A “"” can’t go after this “"”. -- after the calculation is saved
and an error message of -2740.
Can anyone help me please?
We are working on a process for passing certain info nuggets out of a solution (FMP 13) in an encrypted method.
For various reasons a version upgrade isn't feasible. So the plan is to encrypt the nuggets, then pass them into a format for transport.
Currently, we're using Applescript to pass the particular fields into an AES-256-CBC encryption process in a calculated Applescript step, as follows :
The problems which concern me here:
1. The password is "traveling" into Terminal in plaintext. Is there a way this can be viewed during the process (a 'ps' or some other method)??
2. Is there a better method to accomplish this without running as an echo?
I've tried various flavors of this process (successful encryption & transport, etc), but am most concerned about the potential vulnerability from within OSX.. I've run various flavors, then attempted to grep for any of the password strings in log files and Library/Application Support/ folders, but haven't found anything...
Is this an unfounded issue, or should I be going a different direction?
Who Viewed the Topic