>Depending maybe on your fluency. You can do better apps in VFP than in VB you're more fluent in VFP than VB and vice versa. As to the performance, depending on the type of application IMO.

Are'nt most application database oriented i.e. dealing with input and maipulation of data to present the same in a meaning ful way to the end user - a way that makes sense to the end user and enables them to take approriate decisions? Given this as a general "application" why use VFP over VB or vice versa?
>
>>Does this mean that people prefer VB because it has more advantages than VFP?
>VB developers doesn't care much about VFP advantages over VB and same is true with VFP developers doesn't care about VB advantages over VFP. We developers are unfortunate enough because is not an original product of MS. Again it boils down to fluency and the type of application you are developing.
>
VFP must have been appealing to MS to have acquired the product - right?

>It works well with VFP but different approach. In addition, there are built-in tools in VB not available in VFP.

So does going VFP/SQL make the project more expensive/tedious compared to going the VB/SQL route?

>
>>ActiveX controls too? Right?
>1. you can't do ActiveX control in VFP
>2. there are a lot of activeX controls that doesn't work well in VFP especially with controls which has to do with containership.

Meaning VB is a better choice?