I now recall having this issue myself many years ago, and the reason it doesn't work is because the noise words (now called stop words) are not actually indexed, rather than being stripped from the search which is what you assumed. On SQL 2000 you couldn't even use the stop words period or you get an error, so you had to parse the noise file and strip and noise words out of the CONTAINS clause so that they were not used. Obviously the error no longer occurs since SQL 2005, you just don;t get any search results.
Here is a better explanation of full text and stop words for you. http://msdn.microsoft.com/en-us/library/ms142551.aspx -- Russ Michaels http://www.bluethunderinternet.com : B2B hosting, VPS's, Exchange, CF, Railo www.cfmldeveloper.com : CFML community, FREE ColdFusion/Railo hosting http://www.michaels.me.uk : My Blog skype me : russmichaels ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:339478 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
