First Impressions On FileMaker 11 Quick Find Script Step

From Dwayne Wright - Certified FileMaker 10 Developer
WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

CHAPTER 08: Found Set Script Steps

Taking a look under the scripts area under the Found Sets category, you will find that FileMaker 11 has provided us with a new Perform Quick Find script step. It has only one specify option and that is the calculated result you want to use for your search. This means you can hard code a setting, use a passed script parameter, data from a field or even the input from the Show Custom Dialog script step.

I did a movie on this and you can find it on YouTube. The movie is titled, Quickly Scripting The FileMaker 11 Quick Find at http://www.youtube.com/watch?v=yJcKK3D9BVA .

The script step itself is compatible when run from FileMaker Server (as a scheduled event) or via a web browser (using FileMaker Instant Web Publishing). This also means you can create your own Quick Find variations and use them in buttons / custom menus.
=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.

FILEMAKER: New Feature Of Creating Scripts On The Fly

From Dwayne Wright - Certified FileMaker 10 Developer
WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

APPENDIX 3: FileMaker 11

Before FileMaker 11, there was no way to create a new script for a button while you were working with the button. In FileMaker 11, this has changed.

For example, lets say you double click a button and this brings up the Button Setup dialog box and the button is assigned to the action of performing a script. You then click the specify button to pick the script you want.

Here you can see a new bank of buttons that allow you to add a new script, delete an existing script or a multiple use button that brings up a contextual menu of ...

New Default Script
Edit
Duplicate

This is something that is going to be a big time saver for developers. In the past, you would have to close out of the button setup completely, go to define scripts, finish your work there and then come back to your original button setup needs!
=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.

© 2010 - Dwayne Wright - dwaynewright.com

The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.

ADVERTISEMENT ==================
Help support this blog by considering a donating to its ongoing growth. For more details, please visit http://www.dwaynewright.com/donate.html

FILEMAKER 10: Script Triggers And The Debugger Tidbit I Hadn’t Known

From Dwayne Wright - Certified FileMaker 10 Developer
WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

CHAPTER 17: Script Triggers

As you are working on your FileMaker solution, you might have the script debugger open, in particular if you are troubleshooting a script trigger sequence. One thing I didn’t realize until today (and thought I’d share with you in case you didn’t either) is that the FileMaker 10 script debugger will tell you what trigger type fired the script off! Pretty Cool!

=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.

FILEMAKER 10: The Script Trigger Firing Order

From Dwayne Wright - Certified FileMaker 10 Developer
WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

CHAPTER 17: Script Triggers

So you know that you can have multiple script triggers available for a layout and the objects on a layout. You can have so many, it can get confusing what actually happens and when!

Which of these FileMaker script triggers will fire first if all of them try to fire at once? Here is a list of their firing order if all of them were to try and fire at once and a quick note if they are pre / post triggers.

OnFirstWindowOpen (post)
OnLayoutLoad (post)
OnModeEnter (post)
OnRecordLoad (post)
OnObjectEnter (post)
OnObjectKeystroke (pre)
OnLayoutKeystroke (pre)
OnObjectModify (post)
OnObjectSave (pre)
OnObjectExit (pre)
OnRecordCommit (pre)
OnRecordRevert (pre)
OnModeExit (pre)
OnLastWindowClose (pre)

As you can see, the first five triggers are of the post variety. In fact, the only thing interrupting the string are the Keystroke related triggers of OnObjectKeystroke and OnLayoutKeystroke.
=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.

FILEMAKER: Quick Tidbits About FileMaker Script Triggers

From Dwayne Wright - Certified FileMaker 10 Developer
WEB: www.dwaynewright.com
EMAIL: info@dwaynewright.com
TWITTER: dwaynewright
YOUTUBE: FileMakerThoughts

APPENDIX 3: Tidbits

I have a little over 100 FileMaker script trigger questions in my FileMaker Quiz product. Today I was looking at a series of the true / false questions that had true as the answer and thought I’d do a quick post of them here. So here you go ...

-----

If you have multiple FileMaker 10 layout objects selected, you can apply a single script trigger to all of them.

A layout object can have more than one script trigger attached to it.

A field with the OnObjectEnter script trigger can fire when new records are created.

A repeating field with the OnObjectEnter script trigger will fire when tabbing between each possible repetition?

Tabbing into a tab panel will fire an attached OnObjectEnter trigger.

Clicking the tab panel with a mouse will NOT fire an attached OnObjectEnter trigger.

The OnObjectEnter trigger assigned to a portal will fire whenever a different row in the portal becomes active.

OnObjectKeystroke actions are processed after the OS processes and the FileMaker processes.

The OnObjectExit script trigger does not care if a field is modified or not before firing.

A pop up menu can block other events from occurring such as scripts.
=
More info about the author and FileMaker in general, contact me at info@dwaynewright.com.