How to debug script errors in the Forms tool in Groove (922194)

MORE INFORMATION

When the Groove Forms tool calls your scripts, the tool cannot determine whether you have implemented functions except by trying to call the functions. Therefore, Groove uses try-catch blocks, and ignores any errors in the script code.

This means that you cannot depend on the default exception handler to display errors when you are developing and debugging scripts. We recommend that you use try-catch blocks within your functions when you are developing and debugging scripts. Use these blocks to display a message when the script encounters an error.

An example of code that you might use in JavaScript is as follows.

try 
  {
   ... 
  } 
catch (error) 
  {
   GetApp().DisplayError("An error has occurred: '" + error.description + "' [" + error.number + "].");
  }

To debug scripts, you can use the Microsoft Script Debugger, or use another script debugger of your choice. For more information about the Microsoft Script Debugger, visit the following Microsoft Web site: Notes

• Microsoft Internet Explorer does not let you debug scripts after certain errors occur. You know that you are experiencing this issue when you cannot see the Forms tool scripts after you have attached to the Groove process. These scripts should be displayed in the Running Documents window in Microsoft Visual Studio. To recover, exit Groove and any Internet Explorer windows, and then restart Groove.
• You cannot use the Visual Studio debugger to debug script macros.
• You can force Microsoft Script Debugger to break at a particular point in your script. To do this, insert the statement DEBUGGER; at the location that you want.