NOTE: for those who would like to look at this documentation, Kris is talking about the advanced course for FMP 13
this does not seem an error. What they state is that the criteria has to be a literal value. that means that the criteria can be specifically a literal value such as "the first name" or a variable that contains a literal. The criteria could not point for example to another field where it's needed to read that field.
I don't see anything in the Help file that's so precise.
Exercise 30.2 explains how to do Dynamic Finds.
If I am wrong, I hope an expert will tell.
Yea I was re reading the text after my post and I got too hung up on when they said the imbedded find count not be "dynamic".
Sent from my iPhone
...and a reminder that when storing a value in a global field for use as search criteria, you (probably) need to test first whether that value is null.
If you set $middle_name to the value in an empty Middle Name field, for instance, your search script will use "$middle_name" as the criteria, rather than "Betty."
To get around this, I test and substitute a space for null value.
I just did some testing and validated that when $a is an empty string or is not instantiated at all that the query becomes first_name="$a".
FM throws 401 error when "$a" is not found in names::first_name.
it does NOT detect that their is a 400 error just does the text substitute.