Understanding the Microsoft Script Debugger

Debugging VBScript can be difficult and frustrating because the TeamWork Script Editor in TeamWork does not have a built-in debugger. However, you can download and install the Microsoft Script Debugger from the Microsoft Download Center. Although you cannot edit the TeamWork code blocks directly in the Microsoft Script Debugger, it allows you to:

• View VBScript code that has executed when a code error occurs
• View the current call stack
• Step into, over, and out of individual code statements
• Set breakpoints to stop execution
• Evaluate ad-hoc VBScript statements immediately

After installing the Microsoft Script Debugger, you can enable it in TeamWork as described in the BlueCielo TeamWork User's Guide. This adds a Script Debugger item to the Tools menu from which you can select:

• Open: Opens the debugger window with the BlueCielo VB Script code block loaded
• Break on Next Statement: Opens the debugger window with the code block loaded that is associated with the next VBScript statement that is executed

The debugger window also opens when a code error occurs. When you find errors in your code, you must edit it in the Configurator, save your changes, and reopen the vault to load the changed code.

For more information on using the Microsoft Script Debugger, see the online Help in the debugger.