October 29, 2009 at 5:32 pm
I am using the existence of a file to control flow in a package I am designing. To make sure this would work, I set up a SQL task to get a file name from a table, then a File System task that checks the named file. The task operation is Set Attributes, as the other operations caused issues with having to provide details for copy/move options, and I don't want to delete the file.
This appears to do what I need it to - if the file is absent I can follow the "error" constraint path, otherwise the "success" path.
Any gotchas I should know about when using this operation in this way?
Tnx
October 30, 2009 at 8:18 am
Seems like this should work okay.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
October 30, 2009 at 8:25 am
This is also simply achieved with a short piece of script, if you feel like dabbling. This would have the added benefit of not feeling like a bit of a hack 🙂
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply