FIX: Problems Saving DTS Packages to Visual Basic Files Using the DTS User Interface

View products that this article applies to.

This article was previously published under Q293223

BUG #: 235884 (SHILOH_bugs)

Expand all | Collapse all

SYMPTOMS

You can save Data Transformation Services (DTS) packages as Microsoft Visual Basic files using SQL Server 2000. Saving the package as a Visual Basic file codes the package and saves it with a .bas extension. You may encounter the following problems when you save a DTS package as a Visual Basic file:

If the destination drive where the file is being saved has insufficient space, errors may not be reported and a zero byte file may be created.
If the DTS package has an ActiveX script task that contains 50000 or more lines of code, when you try to save the package as a Visual Basic file the process may cause the SQL Enterprise Manager to stop responding (hang).
If a package has multiple steps, and an error occurs in any of the steps, the code may not display any errors to show why the step execution failed.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 (http://support.microsoft.com/kb/290211/EN-US/ ) INF: How to Obtain the Latest SQL Server 2000 Service Pack

Back to the top

WORKAROUND

To avoid the creation of a zero byte DTS file, make sure that the destination folder where the package is being saved has sufficient disk space.
To avoid having SQL Enterprise Manager stop responding while saving a package, save the ActiveX script to a text file and retrieve the text file during run-time.
To provide error reporting for each step of the package execution, invoke the GetExecutionErrorInfo function for each step that is executed within the package.

Back to the top