We use SQL Stored Procedures as our databases for reports. We have input parameters that the stored procedure uses to produce a result set for the report. The report prompts the user for these input parameters.
Prior to Crystal 9, if we added a new input parameter to a stored procedure, all we needed to do was verify database to pick up the new input parameter.
With Crystal 9, verify database does not seem to pick up the input parameter changes. If I do a Set Datasource Location and update my current connection with the changed stored procedure, the new input parameter appears.
A couple of questions:
1) Why doesn't verify database pick up the new input parameter?
and
2) What is the difference between verify database and set datasource location if you are just trying to update the report with an updated version of the original stored procedure the report is using?
Prior to Crystal 9, if we added a new input parameter to a stored procedure, all we needed to do was verify database to pick up the new input parameter.
With Crystal 9, verify database does not seem to pick up the input parameter changes. If I do a Set Datasource Location and update my current connection with the changed stored procedure, the new input parameter appears.
A couple of questions:
1) Why doesn't verify database pick up the new input parameter?
and
2) What is the difference between verify database and set datasource location if you are just trying to update the report with an updated version of the original stored procedure the report is using?