It appears that the same bug that was noticed in CR10 is again appearing in CR XIR2. When using the .Net components and trying to interate thru the parameters, the islinked property of a parameter always evaluates to false no matter how many linked sub reports/parameters exist in the main report. There is a work around noted in KBase Article ID: c2016251 which works for the parameters automatically created by the sub report but will not work for parameters linked to a stored procedure parameter in the sub report. I have many reports I am trying to port from vs2003 asp.net 1.1 with CR 9 to vs.2005 asp.net 2 with CR XI R2 and really need a patch for this. I know that I could rename all my subreport params to begin with "Linked" and then exclude them using the workaround mentioned in the KB. Does anyone know of a patch available for this yet?