Users trying to modify a record being modified by another user will see a dialog to this effect. They are like the Hound of the Baskervilles, which failed to bark at a critical moment and provided the clue to solve the mystery.įileMaker’s own internal codes will spur various dialog messages.
FILEMAKER PRO SCRIPT DEBUGGER ERROR 102 FIELD MISSING CODE
Over 200 built-in error codes exist, including the “no error” error code of zero (0), and the common search result error code of 401, indicating no records were found.Īlthough one might believe it counter-intuitive to include these as error codes, when checking for errors such behavior, it is invaluable. Internally, these take the form of numerical codes, and each code bears a matching text description in FileMaker’s error reference in the Help file. FileMaker Error CodesįileMaker harbors built-in detection and notification of errors. In this brief article we’ll focus on scripting errors, although the methodology applies to all areas: test all features from as many perspectives as possible.
Typically errors occur in the context of scripting through unexpected behavior, although other areas of FileMaker can result in unexpected behavior, including case statements, conditional formatting, autosizing of layout objects, charting behavior, and security. Good solutions find a balance between both methods. The second method attempts to deal with errors that occur and find appropriate ways to minimize the effects. Like defensive driving, the first method attempts to avoid errors from occurring.
Approaches to errors during development generally break down into two methods.
0 kommentar(er)
