THe Caption property is a native VFP property, but it is only assigned a value by the developer. VFP never assigns its value internally.

>The Samples app for Fun with A/A has an example of adding an access method to the caption property. That is where I got the idea to add an assign method to the value property.
>
>I guess we will have to wait and see.
>
>>>I was hoping this thread would lead to tying the A/A to data bound controls. Maybe the next version will fix the bugs with A/A?
>>
>>Not that there are no quirks with A/A, but it is debatable whether or not the malfunctioning Value_Assign method is a bug. I think that the A/A methods were designed to ease implementation details in your custom classes by allowing you to clean up your interface. Giving native VFP properties A/A methods usually gives unexpected results (see a thread last week about Form.Width_Assign), and Value_Assign DOES work, but it only fires when you assign the value yourself, not when the control adjusts its own value via its controlsource or user action.
>>
>>I think you would hear the VFP team argue that this type of application is not what A/A were designed for, and I would not hold my breath waiting for a fix. (But it could happen).