I had a question on executing DTS packages on Win XP/2003.

We developed a DTS package in VB 6 to copy data from an MS Access
(97/2000) database to a SQL Server 2000 database. This standard .exe
package runs fine on Win 2000. However, on Win XP/2003, it runs in a
haphazard manner i.e. it copies some random number of tables and then
hangs. I wanted to know if any one experienced such a problem and how
they resolved it.

Since the source database has around 100 tables, we used SQL Server DTS
Import/Export Wizard to generate the VB code. We created 10 separate
..bas files - one per set of 10 tables - for ease of maintenance. We then
added these files to a standard .exe project.

We created a similar package to copy data from one SQL Server database
to another. It works fine on all 3 OSs mentioned above.

Any help on this would be highly appreciated.

*** Sent via Developersdex http://www.developersdex.com ***

Why do you need to do this through VB?
You are effectively rebuilding a package every time.

Is SQL Server at SP3+?

Can you not just call out to DTSRun and execute a package?

Allan

"male hit" <malehit (AT) hotmail (DOT) com> wrote