>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?

Most application are database oriented but majority of developers do not use VFP because MS doesn't promote it that much.

>VFP must have been appealing to MS to have acquired the product - right?

At that time, RDBMS databases are not yet of full swing and DBFs are still great...

>
>>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?

Again. Depending on your fluency. But VFP/SQL Server is my choice because I ma fluent in VFP.

>Meaning VB is a better choice?

Depending on the application. We use VB in developing interface applications and small non database applications.

VB is not datacentric although you can develop database applications but VFP is far better when it comes to performance. If your app is datacentric go with VFP...