Hi Matt,
Perhaps you're better off by using a custom task to load the current package
path into a variable, and then prefixing the relative paths of the other
packages with this variable... I would think that the current working
directory of the package process is determined by the process calling the
package, and not where the package itself is located.
Regards,
Nils Magnus Englund
<matt.karriker (AT) blackbaud (DOT) com> wrote
Quote:
I want to use execute pacakge tasks in my SSIS solution so that when a
package is called the relative path of the parent package is used to
locate the child package. My first attempt to do this was to remove
the hard coded path when setting up the file connection,
C:\Package1.dtsx replaced with Package1.dtsx. While this works when
executing via designer when executed via dtexecui the connection fails.
Any advice on this one. I am sure there something I am missing but
being new to SSIS I am not sure what i am missing. |