I get the above error when I try and run dts package
saved as vb module - it runs fine as a DTS package on
it's own. It's a simple import of a tab delimited text
file with preceding "create table" execute sql task. I
don't get the same error with the file formatted as csv.
Does vb handle this differently, anyone come across a
similar issue?

thanks

In article <0d9801c35cc9$a0152cb0$a101280a (AT) phx (DOT) gbl>, Bob
<storeybob (AT) hotmail (DOT) com> writes
VB doesn't do anything different, but the VB code is generated and there
may be a bug in the generation routine. This means that the package
built from the VB code may not match the saved package. Try and compare
the code and work out the differences, particularly around the
transforms. Creating a simple test with just one column may help.

You could even write some more VB to load the existing package and
compare it with the one created in code. You could do thing slike
enumerating all tasks, then enumerate all properties checking that they
match.

Another comparison method would be to use VB to build the package and
then save it back to the server. You could then try DTS Compare to show
you differences between the manually built package vs the VB built one.
http://www.red-gate.com/sql/DTS_Compare.htm

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com