With all do respect, this VFP versus VB controversy is tiresome, completely unnessesary and misleading.

The real issue lies with the skill level of the developer.

VFP has some real advantages over VB for developing robust database apps - even with an Oracle or SQL Server backend. But, you gottah know what you are doing to take advantage of the power VFP has to offer. Earlier versions of Fox (FPW 2.6 and earlier) are merely toys when compared with VFP. Actually, it is foolish to compare the two and I would never recommend a FPW 2.6 to VFP conversion unless it is a complete rewrite.

To become skillfull in VFP takes some time and alot of work. There is no way around it. It is more difficult to learn than VB.

The same can be said for VB - you gottah know what you are doing. While VB lacks the native datacentricity of VFP, there are advantages over VFP. I can't think of any at this moment although I'm sure there are some.

Iv'e seen many failed VB projects. Iv'e also seen some real shabby VFP solutions. In all cases, the developers were to blame - not the tool as some would like you to believe.


>Our company currently has an established product written in FP 2.6.
>It has been decided to go a little different way and use a SQL based data engine such as Oracle or SQLServer as the backend with a separate product for the front end. Some of our major stock holders are pushing for the front end to be written in VB. They want this because they perceive it to be a better more stable language than VFP.
>I have been asked to list some pros & cons of VFP versus VB. I don't know much about VB so if anyone can give me some help in this area besides the obvious that switching to VB would require basically starting from scratch. I have already done several conversions from FP2.6 to VFP so I am aware of the problems this can cause.
>TIA
>Mike Yates