Skip to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Creating an Apple script from FileMaker

Featured Replies

Hi,

I want to create an apple script using FileMaker. The File Maker should create any sample.scpt applescript file under my /Users/Application folder of my Mac machine.

I am using a FileMaker installed on my mac machine.

Will the export field contents or export records script step will help me out in creating the required applescript i.e. sample.scpt file...?

The basic requirement is that the generated apple script should execute /run successfully.

Edited by Guest

You could put an AppleScript applet into a container field, as a file. Then you could export it to a known location. Then open it, using an AppleScript in a FileMaker Perform AppleScript step. It would have to be an applet/application/bundle, not a ".scpt", as ".scpt" files do not "run" when you open them, they open in Script Editor, (unless you are using them a source for another AppleScript, but none of that is clear from your post).

But why not just run the whole AppleScript within a Perform AppleScript step? Usually you do not require an external file.

[Mac rant; ignore at your own risk :)-]

As a Mac user, I would have a poor opinion of anyone who thought they had the right to export an applet to my Applications folder, unless they had a darn good reason and documentation to explain the why and wherefore. Also, we expect to be able to move applications wherever we want (within reason). We organize them within subfolders. If an application cannot be moved, then that generally shows that the developer doesn't know what they're doing, which makes their application suspect.

If you mean the "user's application folder," well, I don't even have one. So you would need to create that, in my home folder. Which also would need to be documented.

A better and more expected place for such things as a stand-alone application supporting FileMaker would be within either the FileMaker application folder itself (though that could be wiped if reinstalled); but I think the best place would be within a "FileMaker" folder, within either the startup drive's or the user's Library/Application Support folder. Lots of applications install folders there, with various user-specific bits they need (I have 30 in my drive's one, almost 70 folders in my user one). FileMaker doesn't put a folder in either (though you should check), but you could create one. The path to application support is known to AppleScript.

path to application support

-- alias "Macintosh HD:Library:Application Support:"

path to application support from user domain

-- alias "Macintosh HD:Users:fej:Library:Application Support:"

Yes, my opinions on this may be a bit extreme, but I imagine they are shared by many professional Mac users. If you want to put stuff on people's machines, you need to know the proper place to put them.

[P.S. An added advantage to using one of the Application Support folders is that your average user neither knows nor cares about them. They do not move stuff within them (as they might in Applications), nor do they delete them (as they might with Preferences). That is why this hierarchal structure was created in the first place.]

Edited by Guest
P.S.

I would have a poor opinion of anyone who thought they had the right to export an applet to my Applications folder, unless they had a darn good reason and documentation to explain the why and wherefore.

:exactly:

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.