I have created a DTS package that imports a comma delimited (CSV) text
file into a table. One field uses a VB script that parses a date into
the proper format for the transformation. All other fields are copied
as is. When I run the package directly the date field is imported
correctly (ie MM/DD/YYY). When I schedule the package to run (the job
is in SQL Server Agent, Jobs) the month and day entries are
transposed. In other words the date field is imported as DD/MM/YYYY
(ie Dec 4, 2003 should be 12/4/2003 but the scheduled job imports it
as 4/12/2003)
Does anyone have a fix for this ?

Thanks

"Alan Bell" <belalan@yahoo.com> wrote in message
news:a5344ef4.0312100749.1e59880f@posting.google.c om...
> I have created a DTS package that imports a comma delimited (CSV) text
> file into a table. One field uses a VB script that parses a date into
> the proper format for the transformation. All other fields are copied
> as is. When I run the package directly the date field is imported
> correctly (ie MM/DD/YYY). When I schedule the package to run (the job
> is in SQL Server Agent, Jobs) the month and day entries are
> transposed. In other words the date field is imported as DD/MM/YYYY
> (ie Dec 4, 2003 should be 12/4/2003 but the scheduled job imports it
> as 4/12/2003)
> Does anyone have a fix for this ?

When you run the package directly and when you on it on the schedule, are
you doing both on the same physical machine? If not the agent running on the
server, and you running on your workstation against the server may be using
different regional settings in windows that are causing the erroneous
results.

BV
www.iheartmypond.com