Post reply

Executing package - get previous vbscript from DTS--why?

  • August 2, 2005 at 5:42 pm

    #66477

    I'm not sure that I understand the relationship precisely between vbscript and the file you can save it to.  Are they in a relationship of some kind.  How do I make sure that the package uses the latest and greatest vb script that I put there.  Even when I press OK going all of the way out, it picks up on a previous vbscript (sometimes) when I execute. 

    Is there a place I should save the vbscript so that it can get exported when the time comes to move the packages out to production?

    I don't see anything out on the Internet or Microsoft on this (that I can figure out).  Thanks for shedding any light on this.

    Does upgrading to sp3a make any difference?

     

    Susan

  • August 3, 2005 at 7:04 am

    #579130

    How are you executing the DTS package?? Each time you make an amendment to a package and save it, another version of that DTS package is created. If you are running a package programatically you can explicitly state which version of that package you want to run. Therefore ignoring the most recent version with the changes you just made.

    As a general rule sp3a should most definately be applied to your SQL Server as it contains many bug fixes and security patches.

    Rob.

  • August 3, 2005 at 7:12 am

    #579136

    I am executing the package within designer mode by clicking on package and then execute.

    I want to execute just the latest and greatest.  So I guess I need to figure out how to run the package programmatically so I can 1. delete previous versions and 2. run the latest.  Is that a correct assumption?

     

    Thank you.

     

    Susan

  • August 3, 2005 at 7:28 am

    #579148

    No you will be running the lastest version of the package by default if you execute it from with Enterprise Manager.

    Sounds fishy to me.... if you save the package, close it and then re-open it have you lost all your changes to the script??

  • August 3, 2005 at 7:34 am

    #579151

    No it goes back to the previously saved vbscript.  But if it just acting erroneously, then it was just a question of not saving quite right.  I thought maybe there was a relationship between the vbscript and the file you can save the script to and perhaps therein was the problem.

    So thanks for your patience and I will consider this one resolved for now.

     

    Thanks again!

     

    Susan

  • August 3, 2005 at 10:49 am

    #579235

    Susan

    There is no relationship between the saved VBScript file and the DTS package. The save/load functionality in the ActiveXScript window just allows you to save/load the text. Quite handy if you've got a fairly complex script that has to be changed in a few dozen packages.

     

    --------------------
    Colt 45 - the original point and click interface

  • August 3, 2005 at 11:06 am

    #579243

    That helps a lot.

     

    Thanks.

     

    Susan

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply