In my own experience of using ODBC it has always proved out quite acceptably on all aspects of performance even on files running into 100 MB in size and up.

I have used ODBC frequently, mostly for sending data into MS Excel or Word, to provide clients with self-filling data reports (automatic reporting).

The method I have used to do this to speed the process is to first SQL extract the specifics of the data query from the source file and then perform the intricate SQL stuff on this data extracted file which is in RAM as a "cursor".

Try it and see for yourself. The greatest aggravation I have had has been in selecting the best "DSN" (Data Source Name) file - the system file that represents the ODBC driver configuration - that works with the PivotTable construct ( which I've written in the MS Office products VBA code) which works not only on my office system AND ALSO on my Client's system - meaning correctly setting up the ODBC drivers is essential for success, but I guess that's why we have the opportnity for this kind of work - it challenges the mind. :))
Best wishes, IHTH. /psb.

>Thanks for your answer.
>To tell you the truth, I had an experience of using ODBC but heard
>that it's little bit slow rather than direct access.
>Is it true? and Is it all right with large database also?
>
>>
>>Yes there is --- use ODBC (Open Database Connectivity)- the necessary ODBC connection files should have been installed, and can subsequently be installed, from either your VB setup or from your VFP setup processes or if whether you are in w95 or winnt - go to COntrol Panel and select ODBC driver setup there. Then from inside VB you can use the properties/methods tools to make your connections. If you have Excel - you can do this even easier by using the built in (external Data" tools called "PivotTable". See your help files in VB or Excel for this detail. HTH. /psb.