This Document is not yet Rated

Rate this Document

DIAdem no longer responds when you debug a DIAdem user dialog box.

Primary Software: DIAdem
Primary Software Version: 9.1
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem:

The Knowledge Base item "How to Debug DIAdem User Dialog Boxes (SUD) and DataPlugins" describes how to use an external VBS debugger such as the Microsoft Script Debugger to test user dialog boxes and DataPlugins step by step (debugging).

If you install an external debugger and set the "JITDebug" registry switch, you can use the debugger in DIAdem SCRIPT. Depending on which debugger components you use, the above-mentioned problem may occur in the following cases:

• If you start the debugger in DIAdem SCRIPT and switch to DIAdem REPORT.
• If you start the debugger in DIAdem SCRIPT and call the debugger by setting a "Stop" statement in the user dialog box.

Solution:

To debug user dialog boxes, click the Run Script Ctrl + F5 button to start the script that calls the user dialog box, in DIAdem SCRIPT. When the script reaches a STOP statement in the script code of the user dialog box, you can open the external debugger and debug. In this case, the "JITDebug" registry switch must be set.

To start debugging the script using the Debug Script button, you must disable the "JITDebug" registry switch.

Related Links:

Attachments:





Report Date: 05/11/2007
Last Updated: 05/11/2007
Document ID: 47R0F9H3

Your Feedback!	Poor  |  Excellent							Yes	No
Document Quality?							Answered Your Question?
	1	2	3	4	5
Document needs work? Please tell us why.
Please Contact NI for all product and support inquiries.