I would *GUESS* that you used a SHORTDATETIME field, and indeed it can NOT accept dates prior to 1900.
Look here:
http://msdn.microsoft.com/en-us/libr...7(SQL.80).aspx
Change your field to just DATETIME, instead of SMALLDATETIME, and you can go back to 1753.
(The reason SQL Server doesn't allow dates before that is because it doesn't want to have to figure out the difference between Roman dates and Gregorian dates. But it's a totally BOGUS reason. 1753 is when England (and the Colonies, that would become the USA) changed to the Gregorian calendar. But many many countries changed before that date and several changed after that. So it's a bogus USA-centric decision on SQL Server's part.)
(And why ANYBODY would use a SMALLDATETIME field is beyond me. Oh, sure, there are lots of apps where it will "do", but what are you saving? A whole 4 bytes per record. Whoopee.)