>>>>>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?
>>>>
>>>>Do you compare VBfrontAccess against VBfront-Fox table, or VB-Access against VFPfront-Fox table?
>>>
>>>Excuse my ignorance, but what do you mean when you say VBfront and VFPfront?
>>
>>I meant, did you run query from VB environment against Fox tables, oy you ran it from VFP environment.
>
>Ah, understood. I actually did both. My following replies in the thread have more details

Yes I saw them. What I can tell you. There is always issue of personal preference. If someone is comfortable with VB development environment then it's good for him/her and vice versa. I mean that qualified VB programmers and qualified VFP programmer will probably get similar results in regards to interface development. Now, in regard to query speed. You know the same results (from user's standpoint) can be reached by absolutely different queries. For example, I have two 50K tables (as you have) and I want to bring this data into grid. I can take it simple: make a join, run SELECT, get result. However, I can treat this situation quite differently: I can run query against one table (no joins) and will just diversify Grid.Column.ControlSource to SEEK in another table. Will this faster? Probably much faster. Should we blame or discuss MS role in this or have other global talkings? Probably not.