August 13, 2007 at 10:13 am
I am writing some production installation scripts which make substantial use of DTS packages. Currently, I import some DTS packages, and then manually edit the path depending upon where the customer has installed the application to. Is there a way to automate this such that there is no manual intervention, either through a batch file or VB Script?
Typically I have to edit the Win32 process on an Execute Process Task to point to “C:\Temp\import_trans_and_errorcheck.bat”, but have to do this many times, each with a different path.
Paul
August 14, 2007 at 5:36 am
Sorted.
Just in case anybody is interested; I have created the packages using VB.Net, after initially saving them as VB files. I can then access an environment variable and store the packages requiring no further human input
Paul
August 14, 2007 at 6:42 am
Paul, Do you have time for a quick article for this forum where you show us how you did this? Thanks.
August 14, 2007 at 7:29 am
I will do that later in the week/weekend if that's OK. But it was pretty easy, I have only been playing with D.T.S. for a week, so if I can do it, anybody can
Paul
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy