"Nick Scott" <scottpin@xXxhotmailxXx.com> wrote in message
news:uG5pVO1oFHA.3936@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I'm currently writing a search system in ASP with Javascript connected in
to
> SQL to search a product database. I'm using the FreeTextTable command to
> search a number of fields and bring back results in rank order which is
> working fine. However when the user submits a word in the noise list or
> leaves the search blank and submits SQL returns a nice friendly ODBC
> '80040e14' error.
>
> I've read in FAQs and other posts etc to clear the noise filter and just
> leave a space but if the user enters a space then hits search we have the
> same issue. I'm not happy with that being the resolution and client side
> code to correct this would have to cover the blank, space or multiple
space
> querystring. Instead of this is there not a way in the stored procedure to
> throw something else back before returning what ever it does to bring up
the
> ODBC error? I'm new to stored procedures so not sure if there would be a
way
> to do this breaking out from a statement if it is yeilding a nasty ODBC
> error. If anyone else has any suggestions or examples as to how they use
the
> FreeTextTable predicate to implement a search system through an ODBC
driver
> please let me know.
>
> Regards
>
> Nick Scott
> MCSE 2003
>
>

> Do a replace, replacing these illegal characters. Then check to see if the
> resulting string is =0 characters, if so exit immediately with a return
> code
> that will be interpreted by the calling application as an invalid search
> string.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
>
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Nick Scott" <scottpin@xXxhotmailxXx.com> wrote in message
> news:uG5pVO1oFHA.3936@TK2MSFTNGP10.phx.gbl...
>> Hi,
>>
>> I'm currently writing a search system in ASP with Javascript connected in
> to
>> SQL to search a product database. I'm using the FreeTextTable command to
>> search a number of fields and bring back results in rank order which is
>> working fine. However when the user submits a word in the noise list or
>> leaves the search blank and submits SQL returns a nice friendly ODBC
>> '80040e14' error.
>>
>> I've read in FAQs and other posts etc to clear the noise filter and just
>> leave a space but if the user enters a space then hits search we have the
>> same issue. I'm not happy with that being the resolution and client side
>> code to correct this would have to cover the blank, space or multiple
> space
>> querystring. Instead of this is there not a way in the stored procedure
>> to
>> throw something else back before returning what ever it does to bring up
> the
>> ODBC error? I'm new to stored procedures so not sure if there would be a
> way
>> to do this breaking out from a statement if it is yeilding a nasty ODBC
>> error. If anyone else has any suggestions or examples as to how they use
> the
>> FreeTextTable predicate to implement a search system through an ODBC
> driver
>> please let me know.
>>
>> Regards
>>
>> Nick Scott
>> MCSE 2003
>>
>>
>
>

"zgw" <gwdotnet@hotmail.com> wrote in message
news:u2KqA8MpFHA.420@TK2MSFTNGP09.phx.gbl...
> set a filter to stop certain charactors such as space.
> ok?
>
> "Hilary Cotter" <hilary.cotter@gmail.com> дÈëÏûÏ¢
> news:%233EnWf1oFHA.3120@TK2MSFTNGP09.phx.gbl...
> > Do a replace, replacing these illegal characters. Then check to see if
the
> > resulting string is =0 characters, if so exit immediately with a return
> > code
> > that will be interpreted by the calling application as an invalid search
> > string.
> >
> > --
> > Hilary Cotter
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> > Looking for a FAQ on Indexing Services/SQL FTS
> > http://www.indexserverfaq.com
> > "Nick Scott" <scottpin@xXxhotmailxXx.com> wrote in message
> > news:uG5pVO1oFHA.3936@TK2MSFTNGP10.phx.gbl...
> >> Hi,
> >>
> >> I'm currently writing a search system in ASP with Javascript connected
in
> > to
> >> SQL to search a product database. I'm using the FreeTextTable command
to
> >> search a number of fields and bring back results in rank order which is
> >> working fine. However when the user submits a word in the noise list or
> >> leaves the search blank and submits SQL returns a nice friendly ODBC
> >> '80040e14' error.
> >>
> >> I've read in FAQs and other posts etc to clear the noise filter and
just
> >> leave a space but if the user enters a space then hits search we have
the
> >> same issue. I'm not happy with that being the resolution and client
side
> >> code to correct this would have to cover the blank, space or multiple
> > space
> >> querystring. Instead of this is there not a way in the stored procedure
> >> to
> >> throw something else back before returning what ever it does to bring
up
> > the
> >> ODBC error? I'm new to stored procedures so not sure if there would be
a
> > way
> >> to do this breaking out from a statement if it is yeilding a nasty ODBC
> >> error. If anyone else has any suggestions or examples as to how they
use
> > the
> >> FreeTextTable predicate to implement a search system through an ODBC
> > driver
> >> please let me know.
> >>
> >> Regards
> >>
> >> Nick Scott
> >> MCSE 2003
> >>
> >>
> >
> >
>
>