Date parameter shows error at year 1752

[c8ltgkue]

Hello All

Using CR XI

I have a report which has a date parameter. I accidently entered the wrong date. Instead of entering 01/01/2007 I entered 01/01/1007 and it gave me the following error.

Failed to retrieve data from the database.
Details: ADO Error Code 0x80040e07
Source: Microsoft OLE DB Provider for SQL Server
Description: Syntax error converting datetime from character string.

Then I tried to see how far I could go with the date. Our data is only 7 years old. I tested the report entering the following dates

01/01/2000
01/01/1900
01/01/1800
It worked fine till this point until I entered 01/01/1700 and I got the same error.

Then I played a bit more with the report and found that my report workes fine till the year 1753.

This seems very strange. Does any one know if Crystal has limitation on dates entered in parameters?

Many thanks for you help in adv.

C8

 

[PatriciaObreja]

I think that the error comes from SQL Server which do not accept such old dates as valid dates.

-------------------------------------------------------------------------------------------------------------------------
"Now I can look at you in peace; I don't eat you any more." Franz Kafka, while admiring fish in an aquarium

 

[PatriciaObreja]

Choose the parameter > Edit > Set default values and mark "Range limited field" and enter a Start Date-Time and an End Date-Time that will be valid dates for SQL Server.

-------------------------------------------------------------------------------------------------------------------------
"Now I can look at you in peace; I don't eat you any more." Franz Kafka, while admiring fish in an aquarium