VB requires support DLL's as well... Windows requires ALOT of them...<bg>.Without using VFP objects, there is no data engine per se with VFP ala SQL-Server. There is the ODBC driver. However, if you use VB, you might as well use ADO for your data objects. And, if you are going to go this route, you might be better off with SQL-Server. Then again, VFP all the way around may be a good choice. Two things are certain:

1. The whole DLL argument, any way you slice it, is 100% NOT relevant to
deciding on which tool to use. The idea of "effecting the speed" really
gives cause for concern with regard to the competency of the person or
persons trotting this thoery out...

2. In this post, and the subsequent post, you have not provided nearly enough
of the info required to make an educated and informed recommendation..


>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