Microsoft SQL Server: DTS error, status 6: Data overflow

I'm importing files from a Cegid (kind of foxpro-ish compatible) database.  When I run my DTS package some of the tables import just fine, but others throw multiple errors.  When I double click on the errors, I get a box that says something like this:

Error at Destination for Row number 1.  Errors encountered so far in this task: 1.
Insert error, column 88 ('tv_dsid', DBTYPE_DBTIMESTAMP), status 6: Data overflow.
Insert error, column 87 ('tv_dcap', DBTYPE_DBTIMESTAMP), status 6: Data overflow.
Insert error, column 86 ('tv_dcal', DBTYPE_DBTIMESTAMP), status 6: Data overflow.
Insert error, column 79 ('tv_dcac', DBTYPE_DBTIMESTAMP), status 6: Data overflow.
Invalid character value for cast specification.
Invalid character value for cast specification.
Invalid character value for cast specification.
Invalid character value for cast specification.

I assume this means that the data transformation engine guessed wrong on those particular columns.  So I created a linktable in access to view the data, and Access show that those aprticuar columns are filled entirely with the data "12:00:00 AM". When I open the linktable in designmode Access thinks that field is a "date/time"

Since I'm really new to SQL Server in general, I'm wondering if I could get some expert opinion and assistance working this out.  Any ideas?
AptDevAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SireesCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
SireesCommented:
Problem is  conversion types. Look at the datatypes for Source table and compare them to the datatypes of the target sql server table. if there are any Char to Numeric/Integer or Char to Date and other such assumed conversion then there is your problem.

you can use DTS to handle such errors and use DTS transformation scripts to descide if you want to abort the transfer, ignore the row or create an error file.

You can look at the rows 88,87,86 and 79 to see why it failed?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.