CDOLive LLC The Premier Resource for Microsoft Collaboration Data Objects             


If you are using Microsoft Outlook 98, you can use the Microsoft Script Debugger to test your application. The Microsoft Script Debugger will be installed with Microsoft Internet Explorer 4.x, if you have selected the option Custom/Complete and checked the option Microsoft Script Debugger. Also included in Microsoft Outlook 98 is the Outlook Object Model Browser, which guides you to the development of Microsoft Outlook form based solutions.

Put a STOP (Microsoft Visual Basic Scripting Edition) or DEBUGGER (Microsoft JScript) statement in your code to show the Microsoft Script Debugger. You can then step interactively through your code, execute commands and change values of variables. You cannot change the code while you are in the debugger window. You have to close the debugger, change your code and run the application again.

To check if you have the Microsoft Script Debugger installed, start the Control Panel, choose Add/Remove Programs and search for Microsoft Script Debugger.

To install the Microsoft Script Debugger start the Control Panel and choose Add/Remove Programs, Internet Explorer 4.0, click Add/Remove, select Add a component to Internet Explorer and click Ok. You will be now redirected to the Microsoft Internet Explorer Update Page. This page will show a list of all available Microsoft Internet Explorer components, which can be installed, including the Microsoft Script Debugger. Simply select the Microsoft Script Debugger and start the installation.

For more information about Microsoft Script Debugger, please take look at Links @ Microsoft.

If you are running Microsoft Active Desktop and Microsoft Script Debugger on the same machine, it is possible that your machine will stop responding. The only supported workaround is to disable the Microsoft Active Desktop. An unsupported way is to rename the Microsoft Script Debugger program file (mdm.exe) located at your windows system directory (e. g. c:\winnt\system32). Note that this produces some wired error messages in the Windows NT EventLog, which can be ignored.