This should work fine..I am using the similar one, its working for me...u did anything different ?

This should work fine..I am using the similar one, its working for me...u did anything different ?

This should work fine..I am using the similar one, its working for me...u did anything different ?

The only thing I can think of that might be different is the fact that the value of the parameter is acutally a string. Yes this is not best practice, but that is the format of legacy data. For the param I have a value/name pair, where the value is a short string and the name is a long string. I also tried the following, but still get no results select ... FROM ... WHERE [Field] IN (''''+REPLACE(@Param, ',', ''',''')+''''))Regards Des Norton

The only thing I can think of that might be different is the fact that the value of the parameter is acutally a string. Yes this is not best practice, but that is the format of legacy data. For the param I have a value/name pair, where the value is a short string and the name is a long string. I also tried the following, but still get no results select ... FROM ... WHERE [Field] IN (''''+REPLACE(@Param, ',', ''',''')+''''))Regards Des Norton

I have a report with a number of cascading parameters. these work fine if the parameters are all single select. However when I allow multi-select, the queries suddenly return nothing. Normal queries for single valued params are as follows. select ... FROM ... WHERE [Field] = @Param I then enable the parent parameter to allow multiple values, and change the dependant parameter's query as follows. select ... FROM ... WHERE [Field] IN (@Param) This works, provided that only 1 value is selected in the parent parameter. As soon as 2 or more values are selected in the parent parameter, the child query returns noting. Regards Des Norton

I can get it to work by removing the filter from the query, and adding it as a filter on the parameter. However, this is not optimal as the initial list is large.Regards Des Norton

I can get it to work by removing the filter from the query, and adding it as a filter on the parameter. However, this is not optimal as the initial list is large.Regards Des Norton

Problem solved. The parameter data type nad the source data type were not the same.Regards Des Norton