You can do this using SQL Server, but not ODBC accessing VFP or Access tables. In order to have a client/server system you must have a database server. This means SQL Server, Sybase, Oracle, etc. The difference here is that there is a program actually running on the server that processes your queries and returns the results to the client. If you use ODBC to access VFP data, this is not what happens. The VFP ODBC driver is really just VFP's data engine with an ODBC interface. When you use it, the driver runs on the client. This means you still have to pull more than just the result set over the network.

However, you shouldn't think that VFP will pull an entire table over the wire to return one record. If your query is optimized, VFP can use the index to find the record(s) to return and pull significantly less than the whole table over the network.

>Thanks for the answer. The reason I didn't wanted the second computer from directly accessing the data is to prevent the entire 1 millon records table from going down the network to select just 1 record.
>
>But I thought that it wouldn't be possible with ODBC - after all, MS sells SQL Server! :-)
>
>>You're right with the exception of the part about the shared directory. In order to set up the DSN on the other computer, you'll have to tell it where the data is. If the data isn't located on a share, the other computer won't see it! This is a problem if you're using VFP data and don't want people having full access to the data via other applications other than your own.
>
>Sylvain