jasonlhoward
Programmer
I am using a SQL full-text index search and I'm getting the ADO error: "ADODB.Fields error '800a0cc1' ... Item cannot be found in the collection corresponding to the requested name or ordinal."
The reason I'm getting the ADO error is because SQL Server is producing the message: "Informational: The full-text search condition contained noise word(s)."
SQL Server produces a result set that is perfectly acceptable but the fact that the message is given causes the ADO error. It's very similar to the ADO errors caused when "set nocount" should be set to "on" but is not.
I'm looking for a solution and preferrably the right solution to ignore this particular message or all "Informational:" messages but I would use a solution that ignored all messages.
I've scoured the Internet using my Google and Books Online search skills and not found any information that has gotten me close to a solution. Any help or pointing in the direction of the solution would be greatly appreciated.
One possible solution is pre-filtering the search by removing the "noise words". I'm very concerned about the cpu cycles required because this query is going to be run thousands (maybe even tens of thousands) of times per day. I'm not sure that this is the best solution but it may be the one I have to go with ... I'm not excited about it though.
Thanks for taking the time to read my question.
-Jason
The reason I'm getting the ADO error is because SQL Server is producing the message: "Informational: The full-text search condition contained noise word(s)."
SQL Server produces a result set that is perfectly acceptable but the fact that the message is given causes the ADO error. It's very similar to the ADO errors caused when "set nocount" should be set to "on" but is not.
I'm looking for a solution and preferrably the right solution to ignore this particular message or all "Informational:" messages but I would use a solution that ignored all messages.
I've scoured the Internet using my Google and Books Online search skills and not found any information that has gotten me close to a solution. Any help or pointing in the direction of the solution would be greatly appreciated.
One possible solution is pre-filtering the search by removing the "noise words". I'm very concerned about the cpu cycles required because this query is going to be run thousands (maybe even tens of thousands) of times per day. I'm not sure that this is the best solution but it may be the one I have to go with ... I'm not excited about it though.
Thanks for taking the time to read my question.
-Jason