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

>IMO, this is the biggest load of crap perpetuated today - no offense<g>. If you >want to know what the ActiveX specs are - go to VB - see how controls act and >behave - and you have the specification.

That's like going to Microsoft for the Java spec...(!)

>The bottom line is that VFP is such a small player in this area. VB >consititutes 80% of the RAD tools market. So, that is the benchmark that >ActiveX Control vendors shoot for.

What was my comment about marketing?...

>The issue is testing. If ActiveX control vendors would test their controls in >VFP, we would not have a problem.

Or if they wrote them properly in the first place...

>Perhaps VFP is enforcing the incorrect specficiation. In other words, can a spec be a real spec if nobody adheres to it?

Like ActiveX?...

>Finally, if you are attempting to use an ActiveX Control in VFP - and it does >not work - will it do any good to tell the client that VFP has stricter >enforcement of the ActiveX Control Specficiation???? Somehow, I don't think it >will<s>.

So I should use VB 'cause people don't create proper ActiveX contols?...

>>How much more granular can you get than working with a data set that contains the exact information you want to work with?
>
>It depends on the level of control you need - and the level of abstraction you need. The only way to really see this is to look at things like ADO and SPT. In C/S development, there is a lot more to deal with than just getting data to and from the server.

Yes, there is, *but not from the perspective of the client product*...

>>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...
>
>True, but the technical merits are still there. Trust me, I have tested scenarios in VFP and VB and have seen some amazing things. I am not saying get rid of VFP in favor of VB.

Nor am I saying that VFP is better than VB, only that VFB *would be* if it got as much attention from Microsoft as VB does...

das all i got :)