This is almost always caused by DATE fields that have bad data, say, a date
like 2/5/1099. That date is legal in Access, but not in SQL Server.
Make sure that all of your dates are valid SQL Server dates before upsizing.
From ther SQL Server 7 Books Online:
datetime:
Date and time data from January 1, 1753, to December 31, 9999, with an accuracy
of three-hundredths of a second, or 3.33 milliseconds.
smalldatetime:
Date and time data from January 1, 1900, through June 6, 2079, with an accuracy
of one minute.
To play it safe, you should make sure all of your dates are >= 1/1/1900. If you
absolutely need dates prior to that, then make sure they're all >= 1/1/1753,
and pray the upsize wizard uses datetime. If you need dates prior to that,
(maybe your application is tracking composer birth/death dates), then you have
to use a text field.
