Troubleshooting an issue occurring within a simple script doesn’t pose much of a challenge. As a database grows in complexity, several factors can adversely impact how easily a developer identifies and locates the cause of a scripting problem. A script can call a sub-script, which can call another in a branching hierarchy. Scripts are triggered from numerous interface elements such as buttons, layouts, menus, records, and more. Scripts can jump from one layout context to another, which can be difficult to keep track of during complex processes that are woven into ...
© Mark Conway Munro 2017
Mark Conway Munro, Learn FileMaker Pro 16, https://doi.org/10.1007/978-1-4842-2863-0_36
36. Debugging Scripts
Mark Conway Munro1
(1)Lewisburg, Pennsylvania, USA
Get Learn FileMaker Pro 16: The Comprehensive Guide to Building Custom Databases now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
