Thanks for the reply, JOH. Unfortunately, I checked, and the cdx files
are there. It's strange. The only time it doesn't run correctly is
thru SQL Server Agent as a Job and thru xp_cmdshell in Query Analyzer.
I thought it might be a permissions thing on the dbf files, but I even
copied them to the server that houses SQL and made sure anyone could
access them and still the same thing. I think I'll use C# to add some
data processing stored procedures after the DTS package runs and then
schedule that on the server. What a pain! I feel like I'm duct-taping
it...

Thanks again,
John



*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Funny problem, since you and I are doing about the same thing on the same
server (SQL Server 2000 sp3, and I sure don't have this issue coming up.

You've probably answered the following questions, so feel free to ignore
them.

What sort of path are you using (in the package) to point to the DBF?
I am wondering if you need to use UNC paths (\\servername\andsuch), or
check the shares.

What account owns the package?
Are you sure that in start | control panel | administrative tools | services
that MSSQLSERVER and SQLSERVERAGENT are run by the same logon?
What account owns the job?

Any chance that the CDX files have indexes which aren't jiving with the
DBFs?
I doubt that this is the problem, but no harm in asking.


"John LaPonsie" <john.laponsie (AT) crestoperations (DOT) com> wrote