I'm not sure I totally understand what you are trying to do, but I typically use either the built-in date range options of day/week/month, etc. or I force the user to select a specific date. I've found that unless the parameters are set as internal, the defaults are often not passed to the application. At that point, I just set the default parameter to something simple like Now() and make the report runner choose the specific dates.
What I was trying to achieve was to run one dataset which brings back all the results and then filters basically organise the data.
So I built the query on this basis passing no parameters through instead passing the parameters through to the filters.
The report was basically bringing back a matrix with collapsible fields on all completed tasks with a parameterised filter by team and within a date range i.e. the previous 5 days
There was also a table which just had ALL outstanding tasks and a parameterised filter on team.
The rest were niceties i.e. adding nd, th, rd and st tot heend of dates etc.
The problem I had was that the date comparison I was looking at used the resolveddatetime which included an offset but the value I wanted to pass through was date. All the time this worked in BIDs so I didn't expect any problems but found it didn't work in HEAT so I had to rewrite the query so it included a default offset. Once I got this working I wanted to pass through just a date, got this working in BIDs and then found it only allowed a datetime. I've finally got to the point where it works (sort of) but only by hardcoding a default date into the query but then overiding this if the user enters a datetime, the user still sees a time but this is stripped off. As for the date formatting I started by adding custom code - worked in BIDs but not in HEAT so I rewrote a query nesting about 30 if statements and again works in BIDs but not in HEAT.
Our account managers going to setup a meeting with Randee so that we can discuss the issues I've hit and go from there.
I'm longing for the days of Crystal Reports. It's *very* clear they didn't want to own the reporting aspects of their software, and integration with SSRS is the result.