You might type boyyyyyyyy in the g_search field, and you would still see staff member Lani Boyd, the result of the last successful Quick Find. The error message was suppressed, but, unlike with the Perform Find step, you would still have a found set. What was worse, though, was that when I included the Set Error Capture step, it ended up showing seemingly inaccurate results. Without Set Error Capture, you get the “No records match this find criteria.” Since this script is running each and every time you edit the g_search field, I didn’t want the user to see a multitude of error dialogs I just wanted the found set to become empty. Just like manually using the Quick Find field, no matching records leaves you with the original found set. In most of my solution, users expect they will end up with no records found when they search for something that doesn’t exist.īut the Quick Find step works differently. When I run the script while on some layouts I get a Filemaker error, click continue, then the Show Custom Dialog box shows 401.
Usually, I’ll use the Set Error Capture step to surpress FileMaker’s standard dialog and provide my own custom message. With the Perform Find step, if no records are found you’ll get the error message, but then you will end up with a found count of 0 (unless additional scripting modifies that). With scripted searches, that’s not necessarily true. Either way (unless you modify your search and are then successful), you are left with your original found set. If you get this message in Find mode, you have the opportunity to modify your search or cancel it completely and return to Browse mode using the Quick Find field, you just get the error message.
#Filemaker pro 17 check for find error code#
When manually performing a search, using either Find mode or the Quick Find toolbar field, when there are no matching records FileMaker will alert you with a message stating “No records match this find criteria” (which is error code 401). The problem is, errors with Quick Find in scripts don’t work exactly the way I would expect. As you type, FileMaker filters the list of staff people using the Quick Find feature. The script is triggered by an OnObjectModify script trigger in a global field, g_search. The above script is part of a routine to pop up a window of staff people, select a person, and then use that person’s ID to fill in some other field. The Perform Find step, with two Omit Records actions, was the confusing part:
0 kommentar(er)
