>I just found this in the knowledge base, article # Q164869. It applies to any collation sequence other than MACHINE and sounds just like the problem you're having.
>
>Also, I would advise anyone using SET COLLATE to check out article # Q176884. It describes a bug that can occur when you join tables on an integer field when COLLATE is not MACHINE. This affects every version of VFP and can be impossible to debug. It doesn't happen if the fields are indexed. It bit me the other day becuase I was joining un-indexed cursors. The article doesn't mention it but the problem also seems to apply to using a subquery like this:
>

>SELECT * ;
>  FROM mytable ;
>  WHERE mytable.Key IN (SELECT Key FROM mytable2)
>

Bit me too, some years ago in FPD. Generally, use collating sequences other than "Machine" for strings and strings alone; keep "machine" as default. You'll live longer.