Lesson #9: Fields & Calculations - Logic Functions - Scriptology Mastery Course FileMaker

Without the logical functions, you really wouldn't be able to do much with your FileMaker Pro database. The Logical Functions are what controls the direction of pretty much everything. The direction of your calculations, the direction of your scripts and the direction of pretty much your whole solution. Knowing when to use which logical function over another is a key thing to understand. In this video we cover the must know logical functions and discuss how to use them.

Here's the text expansion tool I use and my own personal set of expansions.

[MyPrivateHub]

Hi Matt, Thank you for your video. I just found that in CASE function, when you want using logical functions AND, OR with values, instead of repeating variable name and adding new value, you can write only values. For example: instead of "~answer = 1 or ~answer = 3;", it's enough to write "~answer = 1 or 3;".

[leewsmith]

You mentioned a DevCon Presentation about the Logical, could you post the name here?

[renderdreality]

A little feedabck that I see many tutorial makers have an issue with. It is simply that "Video is not Radio". A shot by shot explanation of what you are doing on screen isn't necessary. It also makes for a more mentally intense watching experience for your viewer, because the brain is listening to everything and has to then sift out what is important. It becomes a long rapid fire of information. Whilst only explaining the why, would serve the viewer better.

So in short, it we can see that you are clicking a button, you don't have to say: I am clicking the file menu, then clicking the database. We can clearly see that.

[MrDiertje]

haha, you dazzel me Matt.
great video

[GordonBathurst]

Another great Video Matt! Can you please show or reference the shortcut expansion tool you mention while showing the CASE function at around 21:30 .
Thanks,

[filemakermagazine]

IMPORTANT at 44:21 I mentioned that HBH GROUP's use of Evaluate (quote (" "); field1) was dangerous. I WAS WRONG. It is not dangerous. I was misreading the function as if the Evaluate was going to evaluate the contents of field1. If that was the case then it WOULD be dangerous. It does not, however, evaluate the contents of a field. It is only evaluating a single set of double quotes. This type of function is totally benign because you are not exposing the Evaluate function via the user interface. It's a valid way to clear a field.

An alternative way of clearing a field based on the input into another field is this auto-enter calc.

Let ( ~trigger = field1 ; "" )