>>>Hello,
>>> Some of the developpers in our group suggest to use VB 6 instead of VFP 5 in our next project. Their arguement is VFP has to use its own set of .dll files it effects the speed. We should use VB to develop the frond end and use the VFP data engine. Can anyone tell me is there any good study has been done in comparing these two products? Thanks.
>>>sherry
>>
>>Using simple combination of VB front-end and VFP back-end is a very bad choice. It may easily result in extremely slow data processing. The base reason is that only VFP itself can use Rushmore, and without Rushmore and/or native access, it will be slow.
>
>Edward-
>I remember reading this, and seeing it posted several times, but I recently tested hitting a VFP database through an ODBC connection, and the query was DEFINITELY optimized. I am not sure if this is an issue of VFP ODBC drivers, or what.

VFP ODBC does not optimize to the same degree that VFP does. You will find that some queries are only marginally slower, while others are glacial. I had a simple query that ran less than a second in VFP take over 20 minutes through VFP ODBC. Even some of the aggregate functions seem unoptimized. Test any query against the ODBC driver before you ship it. Many queries work as you expect, others fail horribly.