Has anyone run into an issue where a long file name for a source file (particularly DBF 4 or 5) when running the DTS package through development, but when you go to schedule the package so the package is running completely on the server, the import fails because the server can not locate the long filename file. Any specific issue that caused this that I need to update on my server?

When you schedule the package it runs in the content of the SQL Server, when
you run it, it runs as you. Ensure the file in question can be accessed by
the account SQL is running under. If the file resides on a network share
ensure to use the full UNC path.


--
HTH
Ryan Waight, MCDBA, MCSE

"Jason" <otohp (AT) comcast (DOT) net> wrote

but when you go to schedule the package so the package is running completely
on the server, the import fails because the server can not locate the long
filename file. Any specific issue that caused this that I need to update on
my server?