tpomeroy
asked on
Using a Wildcard with a Parameter
I am writing a report that will generate a list of survey recipients. I have two parameters setup: one for the bank acronym and one for job title. My problem is that, if the user enters only "Teller" in the parameter, it will only return Tellers. However, there are job titles like Teller Supervisor and FSR/Teller that should also be returned. I have tried using {Imaging.job_code} like "*{?Job Title}*" but no results are returned with this. What other way can I use a wildcard with this parameter to get what I'm needing?
{@Status} = "A" and
not isnull ({Imaging.NovellID}) and
{@JobTitle} and
(if {?Bank Acronym} = "*" then true
else {@Bank} = {?Bank Acronym}) and
{Imaging.job_code} like {?Job Title}
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Okay, I changed the "allow multiple values" in the parameter to False and the error went away. However, the users really need the ability to enter multiple job titles. Anyway around that?
Not easily that I can think of.
Can you populate the parameter with valid values so they can choose all the ones they want?
mlmcc
Can you populate the parameter with valid values so they can choose all the ones they want?
mlmcc
ASKER
I could but there are hundreds of them. I will try that, though.
You can use the ability to add them from the table rather than having to add them.
If the user enters *Teller* as a value along with another value does it work if you use
{ReportField} LIKE {?Param}
mlmcc
If the user enters *Teller* as a value along with another value does it work if you use
{ReportField} LIKE {?Param}
mlmcc
ASKER
No it does not.
ASKER
error.bmp