Thanks for the reply Sue,
I checked all the file location (you were correct with the UNC
assumption) but all is fine. I finally rebooted the PC last night and
this cured the problem!!! It seems that it was cacheing the file
The problem unfortuanatly has arose again this morning. I am now
looking at last nights data again. I've rebooted the server, and it
all works again but I suspect, at somepoint, the data that is
populating the table will become corrupted again.
I'm completly at a loss as what to do, apart from manually run the DTS
every 5 minutes :-).
> For the text file source, are you using a UNC path to refer
> to this file? The location reference for this file when you
> run the package may not be the same referenced location when
> the package is run as a job. DTS packages run under the user
> context of whoever executes the package. If you run it
> manually, it runs under your user. If you schedule it, it
> runs under the user context of the SQL Server Agent service
> account. The same applies to location - it executes from the
> where it is executed. If you run it from your PC, it runs
> from your PC. When schedule as a job, it runs from the
> server. For more information, refer to the following:
> Q269074 - INF How to Run a DTS Package as a Scheduled Job
> >I have a DTS package that first, drops a table, then creates one and
> >populates it with a text file(csv) from a unix server. This works
> >perfectly and was scheduled to run every five minutes.
> >Now.... if I manually execute the script using enterprise manager, it
> >still works. The problem is, the scheduled run job, is creating a
> >table with incorrect data in it. It runs every 5 minutes but populates
> >the table with incorrect values from another text file.
> >I cannot work out why, when maually run, it works. Scheduled it
> >I am completly lost in what to do (being relativly inexperianced using
> >SQL 2000), so I would much appreciate if anyone could help me.