>>But my problem was to find a way to really join a datatable in memory with tables in the backend. It seems that to dump keys in an in() clause in sql is the way to go. It works when you just have a set of keys, not sure how to deal with that in more complex situations.
>>
>
>We have this same issue with VFP and SQL Server... VFP cursors to join with underlying tables. Very simple within VFP, but not so simple when the database engine is separate. Our solution was to send the cursor to SQL Server as a temporary table, which could then be joined with other tables. It looks like Access has some support for temporary tables, but I don't know the details of how it works.
>
>http://office.microsoft.com/en-us/access-help/create-table-statement-HP001032220.aspx

Thanks Joel.

I would have thought that in VFP when you sql passthrough, you produce a cursor that you can then joinwith vfp tables and/or other cursors.

You can of course create temporary tables in access, but my problem was one of speed and number of access to the back end (from .net). In access you need to do this if you want to be able to open the same form multiple times within an access session. Doable, but desirable? I gave up on Access as a development environment.

Take care,

Marc