Hey.. Does anyone have a solution for the following running 2000:

I have a DTS package (package 'A')that in some cases is calling another
package (package 'B'). When package A is ready to call package B, all
is well. Now I go ahead and modify package B to my liking, and resave
it. Thus, as we all know, package B now contains a new version number
(we'll say version 2 from version 1).

The problem I am running into is that package A is still calling
package B version 1, since that is the one originally selected, and not
updating itself automatically to call version 2.. Does anyone have a
solution for that. I have quite a few packages in this situation and am
hoping for an automatic fix. I have thought about adding a global
variable to all packages called @version_number. I have seen things
about linking versions when it is saved in meta data, but since they
are already saved as SQL DTS package, I dont see an area where I can
move them over..

Any thoughts? Thanks -Danny

phldaniel (AT) gmail (DOT) com wrote:
(http://www.sqldts.com/default.aspx?216)

--
Darren Green
http://www.sqldts.com
http://www.sqlis.com

see.. the problem occurs only some of the time which is where I'm not
sure what is different than another. If I specify a packageID rather
than a versionID, most of the time the call will pick the latest one,
but their are plenty of times that it doesn't, still seemingly to be
dependant on an old version, even though I am specifying only a
packageID, not version dependant.. any help would be great.. is global
variables the way to go? -danny

Hello phldaniel (AT) gmail (DOT) com,

If you simply call the package by name then it should always choose the latest
version.

Allan

Allan,

The keywords you wrote were "it should always choose the latest
version." And, 90% of the time, it does. Unfortunately, I can't
understand why the other 10% of other important executions are not
pulling the most recent versions even though I am pulling the package
ID not version ID .. And, since I need 100% success everytime, I am
being forced against my will to call by versionID so I know it will
work 100% of the time.. Has anyone else had the problem calling
packageID that works most of the time but sometimes it is still calling
the previous version? Here is the versions I am running using
@@version:

Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005
23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Developer
Edition on Windows NT 5.2 (Build 3790: Service Pack 1) ...

Is their a fix for this in a later service pack I don't know about?

Thanks -Danny