In DTS, Microsoft® ActiveX® scripts are optional programs you can add to a package. ActiveX scripts use a scripting language (Microsoft Visual Basic® Scripting Edition, Microsoft JScript®, or PerlScript) and the objects, methods, properties, and collections of the DTS object model to add power, programmability, and customizability to a package. Using ActiveX scripts, you can:
For an ActiveX script to execute, the computer on which the script executes must have the scripting language library installed. The libraries for Visual Basic Scripting Edition and JScript are installed by default with Microsoft Internet Explorer. To write ActiveX scripts in PerlScript, you must install the PerlScript library; see your third-party documentation for more information.
Note ActiveX Scripts and transformations have been fully tested with the Microsoft-supplied Visual Basic and JScript scripting engines only. When designing scripts interactively, note that the functions list box does not enumerate functions; they are hard-coded.
If you have either Microsoft Visual InterDev® 6.0 or the Microsoft Windows NT® 4.0 Option Pack installed, you can use the script debugger supplied with those products to debug your DTS Designer ActiveX scripts. To use the feature, insert a Stop statement in your Visual Basic Scripting Edition code, or a Debugger statement in your JScript code. When the ActiveX script is executed, the script debugger will be opened. If you want to debug multiple ActiveX scripts in a package, select the Execute on main package thread in the Workflow Properties dialog box for the tasks you want to debug. For more information, see the script debugger topics in the Microsoft MSDN Library, Microsoft Visual Studio® 6.0, and the Windows NT 4.0 Option Pack product documentation.
Note Scripts can affect the execution speed of a DTS package. Use them carefully when building a package.