I use CR v.11 connecting via MS OLE DB (ADO)Provider for SQL Server. The Provider uses CR v.10 and has created Automatic software-specific variables for parameters.
"...The CR Viewer will automatically translate a pre-defined subset of parameters passed into a dropdown list populated directly from the database. In all cases, a top-level "-Any Value-" choice is provided to the end user. This choice causes a wildcard value (*) to be passed to Crystal Reports. For this to function correctly, it is recommended that the "is like" comparison option is used when defining the report. In order for the automatic translation to occur, the parameter must be a regular string-value type parameter, and must use the exact variable naming convention as specified...translation is case-sensitive."
I'm still learning Crystal Reports and typically generate a report with a sql command and tweak w/Crystal when necessary.
In following the Provider instructions for example the following parameter will not be accepted as proper syntax in version 11.
ag.AgencyName is like {?AgencyName} -Parameter is set-up as a string value.
I've found a way for it to be accepted on my end and forced the drop down table to appear on the user end, but the query ends with no results. I know the query is correct because if I hard code the Agency Number I get results.
and ag.AgencyName like '*{?AgencyName}' - how I forced it.
Before I was using the single quotes w/no (*) for the wild card and the Provider said that the quotes were nullifying the wildcard so I added the asterisk and the drop down appeared.
We are thinking that there is something going on between the two versions of Crystal.
Can anyone shed some light on this?
Thank you in advance for your input.
"...The CR Viewer will automatically translate a pre-defined subset of parameters passed into a dropdown list populated directly from the database. In all cases, a top-level "-Any Value-" choice is provided to the end user. This choice causes a wildcard value (*) to be passed to Crystal Reports. For this to function correctly, it is recommended that the "is like" comparison option is used when defining the report. In order for the automatic translation to occur, the parameter must be a regular string-value type parameter, and must use the exact variable naming convention as specified...translation is case-sensitive."
I'm still learning Crystal Reports and typically generate a report with a sql command and tweak w/Crystal when necessary.
In following the Provider instructions for example the following parameter will not be accepted as proper syntax in version 11.
ag.AgencyName is like {?AgencyName} -Parameter is set-up as a string value.
I've found a way for it to be accepted on my end and forced the drop down table to appear on the user end, but the query ends with no results. I know the query is correct because if I hard code the Agency Number I get results.
and ag.AgencyName like '*{?AgencyName}' - how I forced it.
Before I was using the single quotes w/no (*) for the wild card and the Provider said that the quotes were nullifying the wildcard so I added the asterisk and the drop down appeared.
We are thinking that there is something going on between the two versions of Crystal.
Can anyone shed some light on this?
Thank you in advance for your input.