Hi Naga,
If CR sets the current date as the default value for date parameters that would be similar to .Net assigning the current date to DateTime controls and DateTime data types. That is not a problem.
I set a filter for a date field in my report and the list of values included 1/1/2001 which is actually 1/1/0001 in the database. I don't have 1/1/2001 in the data anywhere. All my dates in this particular file start in 2013.
According to what I have read in other posts, CR represents 1/1/0001 as 1/1/2001. In other files I will have date fields where some of the records really have 1/1/2001 as their date and others will have 1/1/0001 as their date.
What I see is that if the year of the date is less than 100 (1/1/100) then CR adds 1900 to it. (3/15/54 would appear as 3/15/1954.) There is some other math that happens if the date is 1/1/1 because that is not 1/1/1901 but 1/1/2001. I read about adding 100 in that process.
But the bottom line is that a legitimate 1/1/2001 and a null date (1/1/0001) in the database will both appear on a report as 1/1/2001.
I set up formula fields on my report to print instead of the date. If the corresponding date field is 1/1/0001 then my formula field will be blank. Otherwise it will show the real date value.
If {PRJPF001.AEDT_001} = DateValue("1/1/0001") Then ""
Else ToText({PRJPF001.AEDT_001})
That works well for the output. But record selection is a different story here.