We recently upgraded to Crystal Reports 2010 to SP13, and reports that have been running for years are now prompting the users to enter report values. Oddly enough some reports have started prompting for values while others do not, and there seems to be no difference in the parameter definitions. These are reports that have already had the value set using the SetParameterValue('parametername',value) before being assigned to the Report Viewer. I have tried checking to make sure that the values are being passed as discrete values, as in some cases passing a nullable value does not work, e.g.
If parametervalue.hasvalue then
rpt.SetParameterValue('parametername',parametervalue.Value)
else
rpt.SetParameterValue('parametername',parametervalue.Nothing)
End if
I have also tried using the generated parameter values that come with the underlying report VB to set the values:
With Me.Parameter_InvestorID.CurrentValues
.Clear()
.AddValue(value)
End With
'Me.SetParameterValue("@InvestorID", value.Value) ' old method
Same results - the user still gets prompted, regardless which of these two methods gets used.
I have checked the definitions for the parameters and the following is typical - this parameter example was created by connecting to a Stored procedure in SQL Server.
Name: @InvestorID Type: Number List of Values: Static
Value Field: (None) Description Field (None)
Show on (Viewer) Panel: Do not show.
Optional prompt: False, and will not let me change it.
Default value null
Allow custom values is true
Allow multiple values is false
Allow discrete values is True
Does anyone have any suggestions as to why SP13 should suddenly start prompting users for parameters, when everything was working (barring SP12) up until then?
Thanks, Neil