>>I have been performing some tests accessing both Microsoft Jet databases and VFP 3.0 databases from in VB 5.0. I have seen the Jet/Access databases to be 50% faster at times. Also, when using DAO Dynasets in VB to view query results, I have seen the VB version run 10 times faster than the SELECT in FoxPro. With the ease of development provided by VB 5.0, extreme leanness, and now speed, what place is left for VFP?
>>
>>Has anyone had similar experiences? What are your impressions?
>Gino,
>
>You have not compared using VFP to access VFP and see what the speed difference is there. Try using VB and Jet to access a database that has tables with millions of records in them, for that matter try to get Jet to hold a database that has tables with millions of records in it.
>
>Yes VB is faster at accessing Jet than it is at accessing VFP data, but then VB is optimized to access Jet as that is VB's "native" database.

What I meant by "SELECT in FoxPro" was that I actually performed the query WITHIN FoxPro.

You were correct in that I did not test with millions of records. I was performing a quick test against two 50000+ record tables with a relational join query, which is about the scope of this project. I believe the apparent speed difference may have something to do with the nature of Dynasets, which need not have all the records handy (just their pointers) to return to execution. The records are retrieved as needed thereafter.

If a client needed to store a table with millions of records, I personally would recommend a client-server solution. Chances are, if they were doing that kind of capacity, they wouldn't have much of a problem springing for SQL Server.

Also, I'm sure noone who has used both VB 5.0 and VFP extensively would argue the difference between the quality of the RAD environments.