Yes, using code, not BIDS. We are trying to eliminate as much business logic
as possible from our SQL Server and place in .NET code. The .dtsx packages
are an option but it's my job to explore all options. BIDS is nice but
programming gives us more control.

When you add a Precedence constraint, you add a Precedence executable
(SQLTask1)  and connect it to a Constrained executable (SQLTask2).  It should
be as easy as  pkg.Executables.Item(0) connected to pkg.Executables.Item(1).
However, if the TransferSqlServerObjectsTask is getting jammed in anywhere in
the collection, I run the risk of connection the wrong tasks together if I
loop through the exectuables in the order they are added to the package.

I have a workaround using a FOR but it shouldn't have to be done this way...

   Private Sub LinkTask(ByRef p As Package, ByVal precedenceexec As
Executable, ByVal constrainedexec As Executable)

       'won't enter the For loop the first time this sub is called
       'because no contraints have been set yet
       For Each pConstraint In p.PrecedenceConstraints
           'look for the last task that is constrianed
           If Not pConstraint.ConstrainedExecutable Is Nothing And
pConstraint.PrecedenceExecutable Is Nothing Then
               precedenceexec = pConstraint.ConstrainedExecutable
               'Now look for the transferSQLobject because it gets jammed
in the collection anywhere
               For Each executable In p.Executables
                   If CType(executable,
TaskHost).CreationName.ToLower.IndexOf("transfersqlserver") > -1 Then
                       constrainedexec = executable
                       Exit For
                   End If
               Next
               Exit For
           End If
       Next

           Dim pcFileTasks As PrecedenceConstraint =
p.PrecedenceConstraints.Add(precedenceexec, constrainedexec)
           pcFileTasks.Value = DTSExecResult.Success
   End Sub