Thank you, that worked great. Unfortunately it has created another slight
problem. At this stage in the DTS package I have several CSV's which are
imported simultaneously and after processing , or not processing them all(due
to provided solution) it goes on to do another task using an 'On Completion'
workflow arrow.
The problem is that when I dont execute one of the import tasks due to
filesize being 0, the 'On Completion' workflow criteria is not met and the
package stops executing. All of the files must have been attempted to be
imported previous to doing the processing afterwards.
Thanks for your help.
[quoted text, click to view] "Darren Green" wrote:
> Use this -
>
> How can I check if a file exists?
> (
http://www.sqldts.com/default.aspx?211)
>
> with this-
>
> Working with files and the FileSystemObject - See File Size section.
> (
http://www.sqldts.com/default.aspx?292)
>
>
> --
> Darren Green
>
http://www.sqldts.com >
http://www.sqlis.com >
> "Lee" <Lee@discussions.microsoft.com> wrote in message
> news:8F10B930-6479-48A5-8A4B-136221F445A4@microsoft.com...
> > Just wondering if anyone can suggest any solution to a problem I am
> > having.
> > I currently have a DTS package which is reading in a CSV file on a daily
> > basis, the only trouble is that sometimes this CSV file can be of size 0.
> > Common sense tells you that DTS should notice this and simply read in 0
> > rows.
> > However, DTS fails the step and subsequently, the package. Is there any
> > way
> > to prevent it failing the step due to a file of zero size?
> >
> > If not, is there any way to force the step to succeed once it has failed
> > through an ActiveX script or something similar?
> >
> > Thanks for your time.
>
>