We have a report that has a multi value text parameter, this allows the user to enter multiple strings and the report should produce a listing of all records where the customer name begins with any of the strings entered.
We have created a record selection formula on the customer name field of the form {custname} startswith {?CLIENT}. custname is the database field and CLIENT is the parameter.
If we "show SQL query" this formula is translated as...
WHERE (custname LIKE 'Value1%' OR custname LIKE 'Value2%').
This all works fine and the report functions correctly on the local machine, however the problem is that when we put the report on the webserver and run it through the CR Viewer it does not work when more than one value for the parameter is passed to the report (prompt0=Value1,Value2).
If the parameter contains only one value the report works fine but if 2 or more values are passed no report output is produced. We can see that the correct values are getting to the report by printing out the contents of the parameter in the report header so can only assume that it is a problem with the sql when the report is run via the CR viewer.
We are totally stuck so any help would be much appreciated.
We have created a record selection formula on the customer name field of the form {custname} startswith {?CLIENT}. custname is the database field and CLIENT is the parameter.
If we "show SQL query" this formula is translated as...
WHERE (custname LIKE 'Value1%' OR custname LIKE 'Value2%').
This all works fine and the report functions correctly on the local machine, however the problem is that when we put the report on the webserver and run it through the CR Viewer it does not work when more than one value for the parameter is passed to the report (prompt0=Value1,Value2).
If the parameter contains only one value the report works fine but if 2 or more values are passed no report output is produced. We can see that the correct values are getting to the report by printing out the contents of the parameter in the report header so can only assume that it is a problem with the sql when the report is run via the CR viewer.
We are totally stuck so any help would be much appreciated.