ParameteRR

[GSL]

First of all, I want to say that I love the ParameteRR feature.____I have two questions regarding ParameteRR.____1. When I set up a date ParameteRR, I used the format "m/d/yy". When it prompt for my input, I put 1/1/99 for the new value, then click on Accept. If I went back to this date field, the new value will show as 1/1/2099 and I won^t get any results for the report. Is this a bug?____2. When using characters for ParameteRR, can we enter more than one value so I can do a query say for example, Customer is in the list or in the range ParameteRR field?____Thanks.

[kfleming]

R&R interprets a 2 digit year entry as current century.__It is generally a good idea to use 4 digit year format.____For ranges, you could define 2 parameteRRs and then in your query do >=parameteRRA and <=parameteRRb.____Kathleen__R&R Support

[GSL]

Thanks for your support.____I know I can use >= and <= for ranges, how about useing ParameteRR with in the list?____Thanks.

[Sue_(Guest)]

I have a question on this feature too (and I also am very happy to see it!).____First of all, I want to use a date field in my parameter, and I want to use this same date field in my filter. I am forced to format the date so that it includes the ^time^ in order for it to recognize my field and include it in my filter. Then when I try to run the report I get an error "DB access: (Micorosft)(ODBC SQL Server Driver) Syntax error or access violation"____Here^s my SQL string:__select__ "ID", "EFFDT", "RENTCAT", "AMOUNT", "TAXAMT1", "TAXAMT2", "RENTFLAG", "DESCR", "VENDORID", "INVDT", "INVNUMB"__ from __"dbo".PAYMENTS PAYMENTS __where ((PAYMENTS."ID" like "UWABL003" and PAYMENTS."EFFDT" >= {07/01/2003 1:01:01 am} and PAYMENTS."EFFDT" <= {06/30/2004 12:59:59 pm})) __order by__ "ID", datepart(yy,PAYMENTS."EFFDT") desc______Thanks__