Kristine, I think I may have a solution for you, but I doubt it's a CF problem.
First, you're saying this is just being passed into a query, by which I assume you mean a CFQUERY. But you said in your original note that it throws a "noise word" error. Is that in reference to SQL Server's full text searching? I had asked in my first reply if you were referring to this, or perhaps Verity, or Solr, etc. It helps to know these things in helping solve a problem. Assuming that it's SQL Server's full text search, I've seen some indications that the issue is that it regards the # as punctuation, which it ignores. That generally would be no problem, as it's good for search engines to find words regardless of how punctuation us used (both due to how the searched text may have it, and how one may think to write a search query). But in your example you're left only with the letter C, and apparently it considers that a "noise word" (too frequent to index). Looking into it a little for you, I find there are various solutions. On the surface, some assert that you could remove that c from the "noise word" file, since you DO want to find results searching just for that value. There seem even to be variations of SQL that may work differently (the LIKE keyword vs the FREETEXT function), as well as a matter of whether you're searching with US English or "Neutral" language. But for this specific term, c#, it turns out there may be a solution in a specific update to SQL Server to recognize it, though it seems it may depend on whether you are searching c# or C#. Perhaps one of the ideas above will be a good solution for you. Here are a few places that discuss it more: http://stackoverflow.com/questions/1042/why-doesnt-sql-full-text-indexing-re turn-results-for-words-containing http://www.simple-talk.com/sql/learn-sql-server/sql-server-full-text-search- language-features/ (Search for c# on the page to find the relevant discussion) http://www.eggheadcafe.com/software/aspnet/29440435/c-in-freetext.aspx I'll add that I found these by googling: sql server text "c#" "noise word" I just suggest that because you may have reasonably doubted if searching google for any specific failing phrase would have found much (since it seems a generic sql search problem), but because that specific phrase (c#) is not only a common one where this problem would occur, but more specifically since it turns out there's specific changes in SQL Server to help with searching this very term, it proved fruitful that I tried. :-) Let us know if any of those solve it for you. /charlie PS I hope this note will come through as I send it today, Wed at 2:05pm ET). :-) > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of techsupport > Sent: Tuesday, February 09, 2010 8:25 PM > To: [email protected] > Subject: Re: [ACFUG Discuss] C# question clarified > > I'm the original poster. I didn't get the first, but appreciate any > help so thanks for resending it. I'm still confounded by it but I'm > afraid I'll have to create a new way to write the search. That would be > bad. yes, the keyword of C# is being passed as a variable into the > query. > > I remember years ago being very frustrated years ago why my search was > bombing when i passed variables into the query until I learned about > the very clever "preservesinglequotes" command. I guess I'm hoping > there's something similar that'll work for this. No?? > > ------------------------------------------------------------- To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
