>A coworker is attempting to query (using vb.net) a free foxpro table and join it to a query from sql server 2000 using the 'IN' clause. The query error message returned states that there are too many elements in the IN clause????
>
>Is there an easy way to do this?
>
>Join a foxpro free table with a result from sqlserver? Right now he queries the foxpro table into a temporary table and then queries it looking for in... the sqlserver select.
>
>Is this a limitation of foxpro, the ole provider, or what? If I do a similar query in sqlserver (from two tables) where the in elements exceed 24, there is no problem...

Tell him to check his VFPOLEDB version. However it is not wise to use IN against foxpro unless you are sure the list is short.
A better approach is to create a temp table on SQL server and use it in a join or a linked server.
Cetin