Hi-

I have a DTS package that as part of the package executes a dos batch file for stopping a windows service. I want to be able to check the return code from that step of the packge and see what it says (1,0 etc), if it is 0 great my package can go on to the next step, if it is something else, like 1, I don't want the whole package to fail, but it does right now. How can I work with Error Trapping or some business logic to make this package work better for me?

You can check the step status through code, using the SQL Server DTS library, however, this is more involved. However, if you use success or failure workflow steps, you can route an error through a specific "channel", so to speak.

Brian