If you know you are going to have problems with the dates then can you check
to see whether the data in this attribute is a valid date first?

You could use an Active Script transform that checked the string and decided
not to import the bad rows.

Afterwards you can then do a check on which rows came across and which not.

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Steven" <Steven (AT) discussions (DOT) microsoft.com> wrote

The legacy database enters this date even though it isn't the one that we
want. SQLServer can't handle this date and blows up every time when trying
to copy the data across.