We are trying to import a .csv file that daily has 30,000+
records using a DTS package. Our package works fine all
the time on one PC and gives the error "Column Delimiter
not found" sometimes on another. Once we have a file that
generates this error we can only get it to import from the
PC that it works from all the time. There appears to be
nothing wrong with the delimited file when looking at the
record the error specifies as well as the ones on both
sides of the one specified.

Any ideas of what can cause this? Fixes?

Thank you for your help.

(Build 2195: Service Pack 3). In other places such as
Profiler and Query Analyzer I see this version information
8.00.194. This would appear to be with no service pack
installed.

Do we have service pack 3 or no service pack on the PCs
with Microsoft SQL Server?

Thanks for your help

In article <018401c37187$8cbd3680$a601280a (AT) phx (DOT) gbl>, Neil Sweetman
<neilswee (AT) ix (DOT) netcom.com> writes
<snip>

When running PRINT @@VERSION through Query Analyser the result shows the
version on the SQL Server instance you are connected too (not the
version of the client tools which is important for DTS).

8.00.194 is SQL Server 2000 RTM. RTM is "released to manufacturing", or
no service pack!. I would strongly recommend you update this server,
ideally with SP3a and MS03-031

SQL Server 2000 Service Pack 3a
http://www.microsoft.com/sql/downloads/2000/sp3.asp

MS03-031:Security Patch for SQL Server 2000 Service Pack 3
(http://support.microsoft.com/default.aspx?kbid=821277)


Your problem may originate from different versions of "client" and
"server" software since DTS is client side.

Not sure if there is a decent way of finding out the client-side
version, but for example my dtspkg.dll has a version of 2000.80.760.0
The 760 says to me that this is SP3. Read the SP3 docs and you will see
that the @@VERSION includes 8.00.760 for SQL 2000 SP3(a). Perhaps you
could compare teh dtspkg.dll versions between the "PC" and server.

(http://support.microsoft.com/default...rvicepacks/SQL
/2000/SP3ReadMe.asp)
--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

You can't tell the client service pack level by checking the
versions in the client applications About menu. You can
check a dll or exe properties to get the version. In
addition to going through the service pack readme, you can
match up the version of a file to a service pack level using
the following link:
http://support.microsoft.com/default...on/dllinfo.asp

Enter the file name and the more information link for the
versions tell you what service pack or release correspond to
the version you have.
Not all components are updated on each service pack so there
is no sure way to just figure out the SP level but sometimes
using this is quicker than going through the readme for the
service packs. And if you have multiple client versions, it
can be a pain. sqlgui.dll is usually updated with the SQL
Server service packs though and that can be a good way to
check.

-Sue

On Tue, 2 Sep 2003 12:22:29 -0700, "Neil Sweetman"
<neilswee (AT) ix (DOT) netcom.com> wrote: