>It has to do with 'set ansi'. With OleDb and odbc driver ansi is on (under VFP it is off by default). Both with ODBC and OleDB driver first make a call to:
>
>set ansi off
>
>if you want the behavior as it's in VFP. ie:
>

>OleDbCommand cmd = new OleDbCommand("set ansi off",cn);
>cmd.ExecuteNonQuery();
>

Cetin

Ok, so that explains. Presently, I didn't change that value and adjusted the SQL instead to use LIKE operator instead of =. I'm not sure however if LIKE is has optimized as =.