I have a database and a fulltext indexed table. Lets call this table test. This table has one field called testfield. Now, lets insert only one record as follow: insert into test values ('word' + Char(13) + Char(10) + 'test') This query inserts a word with a LINE_BREAK. Now, lets query this table using fulltext: select * from test where contains(testfield, '"word test"') In that case, this query returns nothing at all. Also: select * from test where contains(testfield, '"wordtest"') Returns nothing (that was expected do be this way) Now, lets query the table again modifying the search word: select * from test where contains(testfield, '"word' + Char(13) + Char(10) + 'test"') In that case the query returns the correct line. The question is: Why does this happen? I mean, SQL should ignore line breaks when searching for a word and it does not. I do not believe that this is the default behavior of a fulltext engine. At least it is not acceptable. What happens if my users insert lines with line breaks on my table (and this is usual, since they can write anything they want because the field is an memo field)? Is there any way of correcting this? **EDIT** It only happens when I choose brazilian as the language for FT. If I choose english, none of the problems I mentioned happens. **EDIT** On Sql Server Denali CTP3 neither english nor portuguese works. Maybe this is bug in the english steamer.