|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Friday, March 20, 2009 10:49 AM
Points: 2,
Visits: 8
|
|
Hi i'm very much a newbie to this but i've been having problems with Microsoft Script Debugger whilst testing ActiveX scripts in DTS. For some reason the debugging stopped working even though the 'Just In Time' box was ticked within the DTS properties. To cut a long story short, i eventually got it working again by changing the DCOM permissions and tweaking the registry slightly.
However i'm still getting the occassional problem with the debugging not working. A blank Microsoft Script Debugger screen appears in the background but doesn't debug my script as it should. A reboot of the server fixes the problem.
Has anyone else experienced this before?
I get the impression that there are better debugging tools to use, can you advise what one i should look at using as an alternative?
SQL Server Properties:
SQL Server Standard Edition 8.00.2039 (SP4)
Operating System: Windows Server 2000 SP4 (displayed as Windows NT - 5.0 in SQL properties?)
Many thanks
|
|
|
|
|
SSC-Enthusiastic
Group: General Forum Members
Last Login: Wednesday, January 20, 2010 7:50 AM
Points: 134,
Visits: 161
|
|
I cannot exactly help you with your script debugger issue but I can offer alternatives to using it.
In the past, I would use a popup box. In the case of DTS, vbscript's msgbox comes to mind. Another good way of revealing things within the DTS environment is to identify all your objects using a loop construct. Often times, when you need to refrence one object while executing within another, you have to have that objects identity context. Running a loop construct against all of the objects (steps/tasks) while msgbox'ng the identity context will allow you to have control over said context - the ability to manipulate said objects properties at runtime.
Good luck and Happy DTSng!
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Friday, March 20, 2009 10:49 AM
Points: 2,
Visits: 8
|
|
Thank you for your reply Mike.
Are we able to use Visual InterDev or something similar instead of the Microsoft Script Debugger?
The less complicated the better, it needs to be available for an inexperienced user 
|
|
|
|
