The Philosophy of FileMaker - Part 3

A introduction to script triggers including simple examples, pre vs post and areas of operation.

Short definitions, some simple examples and associated functions for each script trigger.

Script Trigger behaviors, warnings and general considerations should be aware of before implementing them.

Scripts that trigger at the same time have an order of operation that could affect the outcome.

A simple script trigger that makes navigating layouts easy without utilizing valuable screen real estate.

Use a script trigger to sort a layout automatically no matter how it is navigated.

Three methods for preventing those bothersome carriage returns from being entered into one row fields.

The first part in tracking field modifications with a script trigger is creating the table to store the data.

Before we create the script to store field modification data, we need to decide on the type of trigger and the method for moving the data to the Modifications table.

The final step to tracking field modifications is writing the script and attaching it to fields as triggers.

Providing an iTunes, as-you-type, filter provides a great interface for list view.

Lots of people like record changes to be challenged but let's make sure the message is clear for users who aren't familiar with FileMaker terminology.

When leaving a layout, the active tab panel is lost.

With multiple FileMaker windows, it can be tough to identify the window you want based on the standard window naming numbers.

The OnObjectValidate Script Trigger may not always be used quite the way you imagine.

Script Triggers can solve some of the toughest problems but they can also create conflicts.

Let's improve the bookmark feature by gathering the serial numbers with a loop.

Variables are significantly faster than global fields.

When considering advantages and disadvantages of a solution, speed is commonly a important factor.

By combining the GetNthRecord function and recursion, another approach to gathering serial numbers is possible.

The List option in a Summary field allows you to collect the contents of a field across the records in a found set and store it as a multi-key.

Let's compare and contrast the advantages and disadvantages of the various gathering serial number techniques.

Storing a single found set just isn't practical.

Preventing users from overwriting found sets with the same name is a crucial interface element.

A popup menu and the Go to Related Record script step are enough interface to restore any found set selected from a popup menu.

Let's add the ability to delete a found set to the existing interface.

Let's investigate making the save found set feature adaptive to any table.

If you have a lot of users in your solution, it might be nice to limit the found sets each user can see to just the ones he created.

An entirely different approach to saving found sets can be achieved via the Snapshot Link feature.

A script designed to restore a found set saved via the Snapshot Link feature.

The Snapshot Link feature is significantly more adaptive across tables.

The job of a developer is to make a solution as easy as possible to use for people who aren't as familiar with FileMaker.

By combining two or more functions, more advanced parsing can be achieved.

Regardless of whether you know what a form email is or not, this technique can be applied in so many areas!

The brains of this solution is the calculation formula.

Let's put everything together in a script to finalize the solution.

Let's apply the parsing a form email technique to saving and restoring find criteria.

Restoring the find criteria is almost as simple as duplicating the parse form email script.

Let's investigate how well the find criteria technique adapts to support multiple tables or multiple users.

This brain teaser will increase your problem solving skills.

Mimicking a back button from a web browser requires you to first understand how it works.

The first step to creating a back button feature is storing the layout.

Creating a back button to restore layouts is fairly easy using a straightforward value parsing technique.

A forward button is essentially a back button in reverse.

Why backing through records, files and windows isn't practical.

A general overview of the security features in FileMaker Pro.

Combine the security features in FileMaker Pro along with security best practices to insure the safety of the data in your solution.

Setting up accounts is pretty easy but there are a few gotchas in File Options.

Privilege Sets is the most complicated part of FileMaker security, controlling what accounts can do with records, layouts, value lists, scripts and more.

The Data Access and Design section of privilege sets is the most complicated area!

There are two types of Extended Privileges: default and custom.

This feature allows you to limit access to records on a case by case basis using a calculation formula.

Prevent unauthorized access to your FileMaker files via other FIleMaker files.

Layouts with no access should never be navigated!

Since the data entry account doesn't have access to delete records, let's add some error checking so we don't get a FileMaker error message.

Re-Login is often overlooked but very helpful for efficient testing.

Generating a random password can helpful in maintaining a secure system but will also teach you a lot about how FileMaker works.

Let's combine scripting and security to create a feature for allowing discounted items with manager approval.

The final step for the discount feature is the script to re-login the different users.

Back in Part 2 we created custom menus but never showed how to install them.

Hiding certain window options, positioning your window and resizing windows are important steps for any professional solution.

One script step in particular takes issue with file name changes.

Let's use the $$FileName variable from the previous video to create a feature that adapts to file name changes.

A common open script task is automating the finding of a certain set of records.

Initializing globals in a multi-user solution is essential to user satisfaction.

Seven methods for accomplishing the same task are presented in order to compare and contrast them.

Compare and contrast the seven techniques from the previous video in order to understand how to choose the best approach.

Identifying a duplicate record may not be as easy as it seems given data entry inconsistencies.

A script to efficiently delete duplicates after they have been entered.

Sometimes you want to prevent a duplicate record from ever being entered in the first place.

Cleaning up the tab order is one of the last tasks.

It's a good idea to go through your layouts and clean up the Autosizing objects.

Cleaning up the relationship graph, Script Workspace and layout list are important for the next time you need to work on the program.

Find out about training courses, consulting and solutions from Database Pros.