Ok I am trying to create a flat file connection manager using comma
delimited and " as the text qualifier. The file imports into excel
properly, using import wizard in Sql Server 2000 it formats properly,
using import wizard or flat file connection manager in 2005 it does
not format properly. Below is the sample text that does not parse out
correctly in 2005:

"1419720","ADVENTURES OF FLYGUY, THE (SEASON 1) EP# 0103 ""COSMO NOT/
BRAIN GAME, THE"" (4X3 1.33 FULL FRAME)","PICTURES ENTERTAINMENT
WORLDWIDE PRODUCT FULFILLMENT","3/4/2008"

Instead of 4 columns it splits out into 5 columns in 2k5. The format
of the file looks correct. Any ideas please let me know.
thanks,
Mike

Hi Mike,

<quote> ... 0103 ""COSMO NOT/ BRAIN GAME, THE"" ... </quote>

I suspect the above quotes are causing the , after GAME to be detected
as a new column. SSIS uses the "\" to escape "'s, unlike the vb /
2000 approach of doubling the quote. Try:

.... 0103 \"COSMO NOT/ BRAIN GAME, THE\" ...

*Disclaimer: I haven't actually tried it

Good luck!
J

Hi Mike,

<quote> ... 0103 ""COSMO NOT/ BRAIN GAME, THE"" ... </quote>

I suspect the above quotes are causing the , after GAME to be detected
as a new column. SSIS uses the "\" to escape "'s, unlike the vb /
2000 approach of doubling the quote. Try:

.... 0103 \"COSMO NOT/ BRAIN GAME, THE\" ...

*Disclaimer: I haven't actually tried it

Good luck!
J

Hi Mike,

<quote> ... 0103 ""COSMO NOT/ BRAIN GAME, THE"" ... </quote>

I suspect the above quotes are causing the , after GAME to be detected
as a new column. SSIS uses the "\" to escape "'s, unlike the vb /
2000 approach of doubling the quote. Try:

.... 0103 \"COSMO NOT/ BRAIN GAME, THE\" ...

*Disclaimer: I haven't actually tried it

Good luck!
J

Hi Mike,

<quote> ... 0103 ""COSMO NOT/ BRAIN GAME, THE"" ... </quote>

I suspect the above quotes are causing the , after GAME to be detected
as a new column. SSIS uses the "\" to escape "'s, unlike the vb /
2000 approach of doubling the quote. Try:

.... 0103 \"COSMO NOT/ BRAIN GAME, THE\" ...

*Disclaimer: I haven't actually tried it

Good luck!
J

Hi Mike,

<quote> ... 0103 ""COSMO NOT/ BRAIN GAME, THE"" ... </quote>

I suspect the above quotes are causing the , after GAME to be detected
as a new column. SSIS uses the "\" to escape "'s, unlike the vb /
2000 approach of doubling the quote. Try:

.... 0103 \"COSMO NOT/ BRAIN GAME, THE\" ...

*Disclaimer: I haven't actually tried it

Good luck!
J

Hi Mike,

<quote> ... 0103 ""COSMO NOT/ BRAIN GAME, THE"" ... </quote>

I suspect the above quotes are causing the , after GAME to be detected
as a new column. SSIS uses the "\" to escape "'s, unlike the vb /
2000 approach of doubling the quote. Try:

.... 0103 \"COSMO NOT/ BRAIN GAME, THE\" ...

*Disclaimer: I haven't actually tried it

Good luck!
J

Hi Mike,

<quote> ... 0103 ""COSMO NOT/ BRAIN GAME, THE"" ... </quote>

I suspect the above quotes are causing the , after GAME to be detected
as a new column. SSIS uses the "\" to escape "'s, unlike the vb /
2000 approach of doubling the quote. Try:

.... 0103 \"COSMO NOT/ BRAIN GAME, THE\" ...

*Disclaimer: I haven't actually tried it

Good luck!
J

Hi Mike,

<quote> ... 0103 ""COSMO NOT/ BRAIN GAME, THE"" ... </quote>

I suspect the above quotes are causing the , after GAME to be detected
as a new column. SSIS uses the "\" to escape "'s, unlike the vb /
2000 approach of doubling the quote. Try:

.... 0103 \"COSMO NOT/ BRAIN GAME, THE\" ...

*Disclaimer: I haven't actually tried it

Good luck!
J

Well I could understand that if I had the ability to change the
incoming data, but this is coming from a third party system which i
have no control over.
Still it does not answer the question.. Why would it work in Sql
server 2000 and within excel but not within Sql server 2005?
Thanks,
MM