Has anybody created a custom validator for a valid SQL Server date (1/1/1753 - 12/31/9999). Or are you maybe using a compare validator. If so, what message are you providing to the user.

Right now I have date validators, but a few times users have mis-entered data and ended up with valid regular dates prior to the 1/1/1753 minimum for SQL Server, causing an exception. Not quite sure what message I should give the user and would like to check this client side first if possible.