Of course the real problem is in the application. An ORDER_CREATE date cannot have happened 250 years ago! The application should not be allowing these dates but...
In your case it may be a bad data issue, but it was actually a deficiency in SQL server not to permit data earlier than 1/1/1753. I myself faced problems because of this while migrating date type data from Oracle to SQL Server. In my case, some data in Oracle was stored in Arabic calender (Today's date in Arabic is 25/07/1429)
Even though I tried to solve the issue by converting the Arabic (Hijri) dates to Gregorian as follows
select convert(datetime,'25/07/1429', 130)
2008-07-28 00:00:00.000
the proble still remained. Eventually I had to store the date data in string format in SQL Server for the problematic cases.
This deficiency is removed in SQL Server 2008 which can store date ranging from 1st January 0001 to 31st December 9999.
-----------------------------------------------------------[font=Arial Black]Time Is Money[/font][font=Arial Narrow]Calculating the Number of Business Hours Passed since a Point of Time[/url][/font][font=Arial Narrow]Calculating the Number of Business Hours Passed Between Two Points of Time[/font]