Ok,

Trying to work around the bugs using MS DTS in VB... Cannot use the
"WithEvents" keyword in VB,
soooo,

....cycle through the Stesp in DTS.Package.Steps from the loaded package -
Hooray, everything seems
to execute .. HOLD IT! ...Now the "For Each" loop in VB executes the steps
out of proper order.

Is there anyway to execute the steps IN ORDER the way god intended?

Must I remove every little piece of functionality to execute this animal in
the correct order?

Create constraints between the steps in the package. If one thing needs to
go before A.N.Other then doing this in the package is the best place for it.
This way you simply execute the package and that is that.



--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"Andrew" <afriedl (AT) data-source (DOT) com> wrote

Allan,

The DTS Packages in question have constraints defined. Unfortunately - when
you execute the steps from Visual Basic by cycling through the steps within
a given package - you do not seem to be able to insure that the constraints
are respected.

Although I can execute the entire package, ie, "MyPackage.Execute" I cannot
do so using the WithEvents keyword because THAT methodology is buggy and
prone to explode. I resorted to cycling through the Steps to get better
feedback to my users about what was occurring, and the expected wait (with a
simple progress bar).

Unfortunately, the entire DTS under VB process is sooooooo buggy, that there
is really no other way than to simple execute the base package and hope for
the best - leaving the user to wonder why things are taking so long.

Andrew


"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote