>>What SQLClient are you referring to? What error do you get? Did you check in SQL Server Profiler what has been actually sent o SQL Server?
>
>I succeded to simulate the problem from the SSMS interface. Basically, the problem is at the full text indexing level. I have found that short string such as N/D, N&dd, RT%df, TY=DF, etc., will generate that error when special characters are being used. I just don't know what setting we need to apply so those special characters won't cause any problem. This is a real problem right now as we need this search to work as is.

AFAIK, there're no setting that will help you because almost all special characters are WordBrakers.