The code looks solid, to me. But the CF11 results that you describe - it's as if the database is ignoring the first wildcard.
Have you searched the Adobe bugbase to see if something like this has been posted? I can't think of anything that would cause this. Not even in CFAdmin.
Thats what my gut says to, ill have to look through the bugbase and see if i can find anything
Thank you for your input!
If i use this code to simulate the query in my page : <cfquery datasource="Links" name="data">
WHERE UPPER(PageName) LIKE UPPER('%Form%')
ORDER BY PageName
<cfoutput query="data" >
I get an output of :
Risk Downtime Form 2015 Plan Information 901 Upgrade Information Appeal Form Authorization for Disclosure of Protected Health Information Benefits Information CarePoints Information Drug Information Service Emergency Department Forms Employee Mammogram Form ESA REMS Form Exit Interview Information Exposure Forms Non-Associate FDA MedWatch Voluntary Reporting Form Health Information Release Form Hospital Forms Hospital Formulary - Formulary Kronos System Access Form Leave/Disability Information For Employees Non-Grandfathered Healthcare Reform Preventive Services Order Form - Administrative Order Form - Clinical Order Form - Physical Therapy Order Uniforms Performance Manager Pt Relations Downtime Form Registration Information Resident City Tax Form Scheduling Change Form Scheduling Encumbrance Form Seidman Forms Standards of Performance W9 Form
This is correct as these are all the documents with the word form in it- If i go back to the page that uses arguments.search and type the word form- i get no results
So this leads me to believe it is not the wildcards-but possible the arguements.search
On the page where you call this CFC, can you dump the FORM scope and make sure the value being passed to the CFC method is correct?
Also, and this may not help but would be a good idea from a security standpoint - use <cfqueryparam> to pass the argument in your SQL statements.
It does that with 'form'; but your first example used 'interv'. If you ran the same experiment, are the results the same? Probably, but I'm OCD enough to run it with the original attempted word.
But, really, that's neither here nor there. The issue is happening in real time, as you are typing into the input field. So, as annoying as this will be - before the function returns the results, set up a CFMAIL (spoolenabled, and type="html") that will contain a dump of what the function is getting from the database. Yeah, you'll probably get, like, 50 or more emails, but that will show what the function is GETTING. Then, do the same thing on the page that is displaying the options in the input. That will show what the page is RECEIVING from the function. If they don't match, somewhere therein lies the culprit.
Just my thot.