The Original FileMaker Community
Business Templates - Demo Apps - Video Tutorials -Samples - Help - 46000 Member Forum

The Leading Filemaker Developer Tools

Duplicate A FileMaker Script To Troubleshoot It – FileMaker Today

In the front of the duplicated scripts name, I’ll put in all caps “TEMP:”. This is because sometimes (in the heat of battle), I forget about this duplicate script. To the “TEMP:” naming convention is a useful red flag, so that if at a later date, I can see this it is from an older coding session and is something I need to delete.

Now the preferred way to debug a script is to use the Script Debugger feature in FileMaker Advanced. If you don’t have FileMaker Advance, in the duplicated script, you can put PAUSE, EXIT or HALT script steps to do your troubleshooting. When you’ve fixed the problem, then go back and modify the original script and delete the temporary one.


More info about the author and FileMaker in general, contact me at This email address is being protected from spambots. You need JavaScript enabled to view it..

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More

Privacy & Cookies Policy