>Data binding as we have it in VFP now goes out the window because it is the fact that the controls are fully the responsibility of VFP that allows VFPO to do its data binding. All one has to do is write a VB application with "data bound" controls to see the difference wbetween using the window controls and the VFP controls.

I have to disagree with you. I don't see any reason to lose these advantages if the VFP controls would be "real" windows. I don't know VB, so, I can't say anything.

Still, you may be right and maybe I don't see something...

>At devcon a few years ago Calvin Hsia showed Microsoft Visual Test being used on a VFP application using some code he had written. So automated testing products are possible with the VFP controls.

Yes, that's right. It can be used, but only at bitmap level. This gives much less testing power than the testing when all controls are windows. The testing tools can be used with VFP apps, but they would be much more efficient with "real" controls.

>I will be the first in line to support and beg for widows controls, IF they don't change the ease and flexibility of the data binding we have now. Little thing like having a controlsource, rowsource, and recordsource property. Having those properties available at both design and runtime. etc etc etc

Exactly! This is what we have to ask (beg ? :)) for.

Vlad