>Now... this seems to stick in the craw of many. Why, has the FoxTeam not changed the UI ogbjects so that they are true windows objects. This issue has been blamed on several things that seem to be holding VFP back in the eyes of many... stuff like...
>
>1. Slow Screens
>2. Bad Active-X support
>3. No test tools work with it
>4. Poor performance with NTS... (NTS is the best easiest way to create a thin client product... but, due to VFP's screen handleing, the performance is not up to par with a VB, VJ++, or VC++ front end?
>5. Add your gripe due to this 'anomoly' here!
>

Bob,

Be careful what you wish for. Have you tried to do databinding with VB controls, it is not simply setting a controlsource property.

The history is important in understanding why the VFP controls are as they are, FP 2.X was originally multiplatform supporting DOS, Win, Mac, and Unix. The source code was compatible for all platforms. In order to do that Fox had to control the screen display so it could handle things differently on different platforms.

VFP 3.0 was for Win and Mac, and the same issues applied. The controls became instrumental to the internals of the product. We got a bunch of events and methods that the windows controls don't have. A real lot of code has been written that depends on the events and methods being there and using the inherent data binding capabilities of the controls.

To change these features now would sacrifice backward compatibility of code. That may not be bad thing, but it certainly isn't something to be taken lightly.