I’m experiencing a problem with a VB Script inside a DTS Package. When I
run the task via the Package designer it runs fine. However, when I run the
entire package the result is different.

I need to be able to debug the VB script within the package. The script
uses DTS global variables so I’m unable to run it as a standard script. The
server is a Windows 2003 Standard server running SQL server 2000 standard
edition.

Does anyone have any ideas?

Thanks

I'm using combination of MsgBox and logging values to a couple of
tables through ADODB.Connection.

Vadim.

Larry Bird wrote:
You can use the MS Script Debugger, free download I believe.

Using a STOP statement should allow you to attach to the process. This
is not always 100% reliable, but a MsgBox will pause execution and you
can attach then.

Check the properties of the DTS node in EM, there is a JIT debug option
I think, probably need to turn it on. (It has been a while...)


--
Darren
http://www.sqldts.com
http://www.sqlis.com