Jim,

About all I can say to that is: With VFP focused on mid-tier, it will ever be thus.

Which is unfortunate, because many product vendors take the approach that their product *will* best the competition some day soon. Clearly MS does not, leaving the small/medium business to VB+ADO (now that it exists) and leaving VFP for the Enterprises, *IF* they elect to use it over other competitors.

Cheers,

Jim N

>Jim,
>
>Comparing the UI capabilities of VFP with those of VB is like comparing a Ford Escort to a Porche. VB outclasses VFP is just about every aspect of UI development.
>
>1) VB uses real windows controls so all of the third party auto testing programs work with it. VFP uses VFP controls that windows cannot see nor does windows know anything about them.
>
>2) Citrix and other remote access systems work well with VB, they are abysmal with VFP.
>
>3) All of the ActiveX controls work with VB, some work with VFP.
>
>4) VB forms load many times faster than an equivalent VFP form (even without data binding).
>
>5) VB has a smaller memory footprint than VFP.
>
>So the argument that VFP is Always the best tool is a nearsighted view of things. If an applciation's major requirement is a fast and responsive UI then VFP is NOT the right tool, VB or VC++ would be.