The script debugger is part of FileMaker Advanced and it has a series of control buttons at the top, an area to view the script details and an area that tells you a little bit about the active script that the debugger is looking at.
I really didn’t pay that much attention to the lower area that shows the active scripts until recently. This area shows you the active script name, the file that it resides within and what parameter may have been passed to it. This wasn’t that big of a deal to me because I tend to know this information already because I programmed the script and my comments tend to tell me this information. Honestly, I don’t spend a lot of time debugging my scripts in this manner. I tend to take a little more time writing my scripts, I comment them heavily and I run them right after I create them.
However, I have been working on some databases created by others and this area is becoming more important to me. The previous developer setup routines that have a huge number of scripts calling upon subscripts and the Active Script area began to make more sense to me. This is because the Active Script Area can be more of a historical reference if you have a script that calls upon a lot of subscripts. Every subscript adds to the information in this area, so you see a kind of subscript log.
Now you will have to use the Step Into button on the debugger or you simply loose the historical account of the subscripts being called upon. If you do step into your subscripts via the debugger, each script executed gets pushed down into the active scripts display and the current script at the top in bold.
Here you can see a script that calls upon a subscript, that calls upon a subscript, that calls upon a subscript, that calls upon a subscript. In each instance, a different parameter was passed to the following script.