Itc1,
As the others have said, forget about ODBC. Regardless of the overhead imposed by the driver, ODBC won't help in this case because Visual FoxPro is not a true client/server database. That means that the record selection is actually performed on the client machine, so there is no benefit of moving to ODBC.
You would, however, get a lot of benefit by moving to a true client/server back-end, such as SQL Server or Oracle. That would get rid of the overhead caused by the network, but it would mean a great deal of redesign and re-programming of your application, not to mention financial costs, so it is not something to be done lightly.
I think your best bet would be to focus on the design of your database, and particularly to check that all fields that take part in WHERE clauses, LOCATEs, filters, joins, etc. are properly indexed.
Mike
Mike Lewis
Edinburgh, Scotland
My Visual Foxpro web site:
My Crystal Reports web site: