Hummm... I'm still researching, but what I have determined so far is that
the Dynamic Properties Task IS ALREADY setting the properties for ALL
connections in the job, but at runtime, it "appears" to be using the value
on at least 1 connection to access the tables on the server that is
hardcoded in the design time object. I iknow this because we use a table to
control many external parms (a name/value lookup table) like date parms.
Current date would be a value of '0'. We accept offsets (-1, -2, or
specific dates like '20050311'. I overrode the table on the local server to
use a hardcoded date, ran the DTS job and received the errors you get when
logic gets value from the table, and if NOT a dfarte, but an realtive date,
it tries to add the offset amount to current date then do date compare edits
on rest of data. It was retrieving a value of +0 from the wrong server...
DTS says it is in fact supposed to use the INI file to plug in the name of
the local server, and it didn't behave that way.
I'm not sure, but think I'm worse off now than I was originally...now it
appears "code" right, behavior is wrong.
[quoted text, click to view] "doug" <dsmrtn@pacbell.net> wrote in message
news:#bUZntWKFHA.3960@TK2MSFTNGP09.phx.gbl...
> Okay, reading more. It would appear the objects I'm concerned about don't
> have design time properties that can be exposed, but the Dynamic
Properties
> Task can still be used to change their properties at run time if you add
> them to the list. Going to give it a try.
>
>
> "doug" <dsmrtn@pacbell.net> wrote in message
> news:#nC#kPWKFHA.436@TK2MSFTNGP09.phx.gbl...
> > This is what is already being done. It works fine for the 'Execute SQL
> > Tasks' tool, but not the 'Microsoft OLE DB Provider for SQL Server' tool
> or
> > the 'Copy SQL Server Objects' tool which don't seem to support global
> > variables (at least I haven't been able to expose them).
> >
> > doug
> >
> >
> > "Tim" <mitsirrah@netzero.net> wrote in message
> > news:1110857319.692761.239960@o13g2000cwo.googlegroups.com...
> > > You could use a Dynamic Properties task to modify the properties of
all
> > > of your connections as the first step in the package. That task could
> > > read out of an *.ini file, or you could make the assignment by global
> > > variables which could be passed in at the time that the DTS package is
> > > executed (use dtsrunui.exe to see how to call a DTS package and pass
in
> > > the values for the global variables).
> > >
> >
> >
>
>
