SNIPPED

Jim,

More of 'outsiders' making the excuses for the MS/VFP folks. We absolutely must learn to let them speak for themselves!

But considering your response: Why could not MS (the Win folk, I suppose) give MS VFP folk the capability to sub-class the standard WIN objects to endow them with the 'missing' events, methods and properties??? Sure, this would not be the "sub-classing" that we app developers are used to, but it could be done nonetheless.

Nothing is impossible, but there *MUST* be a will. I feel strongly that it is up to the real users of the product to give them that WILL, and that it certainly is NOT the product user's responsibility to make an excuse every time someone dares to dream a little.

Jim N

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