Hello all!!!
I have the following problem using SQL DTS package scrit executed within
Visual Basic.

The data source is a Text File.
The file type is ANSI
The file format is Delimited
The row delimeter is vbCrLf

When the package is executed, I get the error "Row Delimeter not found". But
this happens only on a spicific pc. On mine it works fine.
While trying to work it out, I have found out, that the error happens when
there isn't a vbcrlf (return) character at the end of the file.
Which could be that setting that makes my pc different and the package is
executed without errors?

Thank you.

Telemachos

is it a separate DTS packages on each PC?
if so,
i would assume that one of the DTS packages has {CR}{LF} and the
other hasnt

if not.

try setting it to <none> and see if it helps.

hb



"Torrio" <Torrio (AT) discussions (DOT) microsoft.com> wrote

Hi again!
As I mentioned in my mirst msg, the DTS package is executed within VB6.
Anyway, if I save the package on the SQL Server and each user tries to
execute it within Enterprise Manager, the problem is still there.
SAME DTS PACKAGE EXECUTED FROM DIFFERENT PCs.
Your suggestion, cannot be done bacause there is no "none" option.
I think this is some kind of bug...
When I open the Package in Enterprice Manager, (on the pc that it works
fine, executed from VB), I open properties of Connection 1 and when I press
Properties button, then Next to see the file's records, I get the message
"Could not find the selected Row Delimeter within the forst 8Kb of data. Is
the selected delimeter valid?" Then I press Ok and the records of the file
are shown fine.
I repeat: On that pc it works when executed from VB.
I assume that it's a configuration that must be changed in order to work the
same everywhere.

Thank you!

Telemachos


"hb21l6" wrote:

Torrio,

What is the path of the file which is being imported? If you are using
a non-network path, then each machine that executes the DTS package in
Enterprise Manager, might be looking for a local version of the file,
in that case, the one machine that is getting an invalid row delimiter,
may have a slightly different version of the file. One option is to
copy the file locally, scrub the file so it is exactly what you expect,
load the file, and then delete the copy. I have had to do that to
solve this same issue.

Dustin