Hi Mike,

SQL Server 2000 used the VB escape method of double quoting - so ""
for " instead of \" .. if that makes sense

In this case I suspect you will need to manually split the columns.
In fact, if I take the sample row above and try to create a flat file
connection to a file containing that row I get a warning stating that
the row contains text qualifiers and will produce an error at runtime.

I would recommend configuring your file connection to just have 1
column, and then use a script transformation task to split the data
into columns.

Good luck!
J

Hi Mike,

SQL Server 2000 used the VB escape method of double quoting - so ""
for " instead of \" .. if that makes sense

In this case I suspect you will need to manually split the columns.
In fact, if I take the sample row above and try to create a flat file
connection to a file containing that row I get a warning stating that
the row contains text qualifiers and will produce an error at runtime.

I would recommend configuring your file connection to just have 1
column, and then use a script transformation task to split the data
into columns.

Good luck!
J

Hi Mike,

SQL Server 2000 used the VB escape method of double quoting - so ""
for " instead of \" .. if that makes sense

In this case I suspect you will need to manually split the columns.
In fact, if I take the sample row above and try to create a flat file
connection to a file containing that row I get a warning stating that
the row contains text qualifiers and will produce an error at runtime.

I would recommend configuring your file connection to just have 1
column, and then use a script transformation task to split the data
into columns.

Good luck!
J

Hi Mike,

SQL Server 2000 used the VB escape method of double quoting - so ""
for " instead of \" .. if that makes sense

In this case I suspect you will need to manually split the columns.
In fact, if I take the sample row above and try to create a flat file
connection to a file containing that row I get a warning stating that
the row contains text qualifiers and will produce an error at runtime.

I would recommend configuring your file connection to just have 1
column, and then use a script transformation task to split the data
into columns.

Good luck!
J

Hi Mike,

SQL Server 2000 used the VB escape method of double quoting - so ""
for " instead of \" .. if that makes sense

In this case I suspect you will need to manually split the columns.
In fact, if I take the sample row above and try to create a flat file
connection to a file containing that row I get a warning stating that
the row contains text qualifiers and will produce an error at runtime.

I would recommend configuring your file connection to just have 1
column, and then use a script transformation task to split the data
into columns.

Good luck!
J