>
>This is mostly a guess, but I bet that the SET ANSI setting is ignored when accessing the data through ODBC. The VFP ODBC driver is probbly deciding how the strings are compared, and attempting to emulate how most datasources handle this, by doing an exact string comparison. Try LIKE instead of =.

Before I do my requery, I set the ?value to be '%'+cTheValue+'%' and in the SQL of the view I used LIKE instead of = and it worked.

I worry now that this isn't optimized since it's using LIKE (it's now a substring search).

Of course, I also worry that I am getting C0000005 when I do little things like updating default table field values in the DBC....