Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
JScottP99
Starting Member
5 Posts |
Posted - 2006-03-14 : 12:00:20
|
I receive a text file that must be imported into an existing table. I have created a DTS package for the import but I have run into the following issues:1. The text file is comma-delimited but within the data there may be a comma such as 'lastname, firstname' once my DTS package hits a row such as this it errors on that row and stops.2. If I go into Options and set the Max Error Count it will error on every row following the bad row, even though the following rows contain no bad data.How can I get around this issue without having to become a DB Programmer. You may be able to tell that I am definitely a newbie at this. |
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2006-03-14 : 12:14:50
|
Can you get the text file with a different delimiter, such as tab or pipe or even *? If so, this would be the easiest solution.. |
 |
|
JScottP99
Starting Member
5 Posts |
Posted - 2006-03-14 : 12:22:23
|
quote: Originally posted by RickD Can you get the text file with a different delimiter, such as tab or pipe or even *? If so, this would be the easiest solution..
Unfortunately, no. The program that produces the text file produces multiple files for multiple uses. I've been told that "this is the way it is."I wouldn't mind if the DTS Package would just skip that row and continue to the next, but it just keeps erroring on the following rows. |
 |
|
|
|
|