>>>>>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.
>>>>
>>>
>>>
>>>Do do I Vlad.
>>>Having written lots of VB apps I prefer the VFP DE with responsible controls to the way VB does it.
>>
>>So what are Access controls? They have similar data binding. Are they hand-painted like VFP objects, or standard windows objects like in VB?
>
>
>I was refering to using Access as a backend to VB. I never have nor would I ever program an app using just Access.

I brought up Access because of this pseudo-syllogism:

1. Access uses Visual Basic for Applications (VBA)
2. VBA is based on VB
3. VB has real windows objects, not painted-in ones, according to people here.
4. Access controls have .controlsource properties, and Access listboxes and combos have .Rowsources, just like VFP.

Therefore, I suppose that Access has real windows objects, and that such objects can have the data binding we like.

Or maybe not.