Reputation: 441
I have a parameter that allows multiple values. Its for a name field in my database. What I want to be able to do is allow the user to put in a name and then have crystal find any name like any of the names they entered. So for example you could put in 4 last names and crystal would return anyone who had any of those names in the name field. I can get the "like" to work just fine, but only when there is one string in the array. Here is my select formula:
numbervar counter := 1;
numbervar positionCount:=count({?Customer Name}); //I'm not sure what to put
here. Count? UBound?
if {?Customer Name}[1] <> 'ALL'
then
(
while(counter <= positionCount)
do
(
{NAMEFIELD} like '*' & {?Customer Name}[counter] & '*';
counter := counter + 1;
);
)
else
if {?Customer Name}[1] = 'ALL'
then
true
)
This formula returns all of the names, not the ones in the parameter. Any ideas on what I'm doing wrong?
Upvotes: 6
Views: 29332
Reputation: 26262
Another approach (I thought it made sense to create a separate answer), if you have Oracle, is to make use of the REGEXP_LIKE expression.
SELECT customer_name FROM customers WHERE ( '{?QUERY}'='ALL' OR REGEXP_LIKE(customer_name, '{?QUERY}') )
'A|B|C'
is equivalent to LIKE '%A%' OR LIKE '%B%' OR LIKE '%C%'
.Upvotes: 0
Reputation: 26262
Create a multi-value parameter ({?Customer Name}) with these properties:
Add a row to the parameter's pick-list grid; supply 'ALL' and 'ALL' (without single quotes)
Create a Custom Function (named 'Delimit') with this text:
// Delimit()
// enclose each value in array in **, returning an array
Function (Stringvar Array params)
Split("*" + Join(params, "*,*") + "*", ",")
Modify the report's record-selection formula:
If {?Customer Name}<>"ALL" Then
{TABLE.CUSTOMER_NAME} LIKE Delimit({?Customer Name})
Else
True
Optionally, create a formula to display the parameter's values with this text:
//{@Customer Name}
Join( Delimit({?Customer Name}), ";")
Upvotes: 4
Reputation: 7287
Luckily CR can handle this situation automatically (at least in CR2008, where I just confirmed it). You can just do {?Customer Name}="All" or {NAMEFIELD} like {?Customer Name}
.
It will be up to the end user to use the wild cards appropriately, but you can add a blurb to the parameter's help text or force the *Name* format with an edit mask.
Upvotes: 2