I have the developer edition of SQL Server 2000. I also have a DTS package
that imports from a text file into a SQL Server 2000 database table using the
standard ODBC driver for SQL Server supplied with DTS. It worked fine UNTIL I
added ONE column to my destination list in order to import further columns
from my source text file. The resulting package TESTed fine while outputting
to the TEST text file. However, when I actually ran the package zero-or-one
row was imported, rather than the 50 or so rows I expected.

Note that it doesn't matter WHAT column I add to the selected destination
list: ANY such added column causes import failure.

Any idea what's going on here?

ERRATUM: I should have said "the standard OLE DB Provider for SQL Server"
instead of "the standard ODBC driver for SQL Server", below.

"PhilEngle" wrote:

"PhilEngle" wrote:


the dts packages run flaky if you change them - I always rebuild new ones
with any changes - they always work cleanly on a rebuild...... (sometimes you
can just rebuild a section of a package and its OK) - i.e. transform data
task - in between 2 conns.