>As for deciding between VFP and VB, it depends. From a UI standpoint, if you >need ActiveX support, thing long and hard before comitting to VFP. Fact is, >many ActiveX controls do not work correctly with VFP. This extends to controls >that ship with Visual Studio.
>...
>Yes, VFP has OO and VFP's object model is much better than VB's object model. >But, if you can't get an ActiveX control to work correctly, who the heck will >care about OO<s>.

It's my understanding that the reason for this is that VFP requires ActiveX controls that adhere strictly to the ActiveX specifications, and that many ActiveX controls don't...


>As far as data access goes, remote views in VFP are highly overrated as the >granularity of control is not there.

How much more granular can you get than working with a data set that contains the exact information you want to work with?

>...

You go on to make a number of other points which I don't feel qualified to respond to, but find difficult to swallow nonetheless. Just goes to show that when MS throws enough marketing money into anything they can get people to buy it...