PRB: Errors May Occur When You Use SQL Server 2000 to Save a DTS Package as a Visual Basic File (293164)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
This article was previously published under Q293164

SYMPTOMS

SQL Server 2000 has the option to save a DTS package to a Visual Basic file. If a Microsoft SQL Server 7.0 package is saved as a Visual Basic file by using SQL Server 2000 tools, it may cause several run-time errors if you execute the Visual Basic script on a computer that has SQL Server 7.0 and Microsoft Data Access Components (MDAC) 2.5 installed.

WARNING: Do not install MDAC 2.6 on a clustered Microsoft SQL Server 6.5 or 7.0 server. SQL Server 6.5 and SQL Server 7.0 clusters do not function properly with MDAC 2.6.

CAUSE

The save to Visual Basic file option is a new option available in SQL Server 2000 and it always generates code to invoke a SQL Server 2000 package.

If a package created on a SQL Server 7.0 computer is opened on a SQL Server 2000 computer, and then saved as a Visual Basic file, the file is generated using the properties of the SQL OLEDB provider that is provided with MDAC 2.6.

WORKAROUND

To work around this problem, use any of the methods that follow:
  1. Install MDAC 2.6 on the SQL Server 7.0 platform if the SQL Server 7.0 server is not clustered. Please refer to the warning in the "Symptoms" section before you install MDAC 2.6.
  2. Edit the Visual Basic .bas file and comment out the offending properties before you run the package from within Microsoft Visual Basic.
  3. Use the Scriptpkg.exe tool that is provided with SQL Server 7.0 (located in MSSQL7\DevTools\Samples\DTS\DTSDemo.exe) to script SQL Server 7.0 packages into Visual Basic code.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000.
Modification Type:MinorLast Reviewed:3/24/2004
Keywords:kbBug kbpending KB293164
©2004 Microsoft Corporation. All rights reserved.