![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a dts package which needs to branch depending on the existence of a certain text file. Currently I have an Activex VBscript step which returns Success if the file is found, and Failure if it is not found. I have established work-flow based on this. But when the Activex returns Failure the entire package fails. I see no way to prevent this from happening. That being the case, why does DTS provide the "On Failure" workflow? No, I have not set the Step's WorkFlow to Fail the package on Step Failure. |
#3
| |||
| |||
|
|
I have a dts package which needs to branch depending on the existence of a certain text file. Currently I have an Activex VBscript step which returns Success if the file is found, and Failure if it is not found. I have established work-flow based on this. But when the Activex returns Failure the entire package fails. I see no way to prevent this from happening. That being the case, why does DTS provide the "On Failure" workflow? No, I have not set the Step's WorkFlow to Fail the package on Step Failure. |
#4
| |||
| |||
|
|
You do not need to fail the package to accomplish this in fact you do not need to return an error at all. You simply say If the file does not exist disable the task following this or branch down this particular path It is not much different to this Looping, Importing and Archiving (http://www.sqldts.com/default.aspx?246) or this one might be easier to understand- |
#5
| |||
| |||
|
|
You do not need to fail the package to accomplish this in fact you do not need to return an error at all. You simply say If the file does not exist disable the task following this or branch down this particular path It is not much different to this Looping, Importing and Archiving (http://www.sqldts.com/default.aspx?246) "Snake" <Snake (AT) discussions (DOT) microsoft.com> wrote in message news:Snake (AT) discussions (DOT) microsoft.com: I have a dts package which needs to branch depending on the existence of a certain text file. Currently I have an Activex VBscript step which returns Success if the file is found, and Failure if it is not found. I have established work-flow based on this. But when the Activex returns Failure the entire package fails. I see no way to prevent this from happening. That being the case, why does DTS provide the "On Failure" workflow? No, I have not set the Step's WorkFlow to Fail the package on Step Failure. |
![]() |
| Thread Tools | |
| Display Modes | |
| |