>Send to VFPfeed status:
>Never it will not be sended.
>
>Subject:
>A Protected Object does not allow directed use of one its property in its ControlSource.
>
>Versions : VFP8SP1 and VFP9.1720
>
>Observed:
>If you call a SetAll() from the outside, no error happens.
>But from inside VFP it put into the set list the protected object
>and it fire an error when it tries to write within the property.
>
>Expected:
>A setAll ignore the protected objects.

Fabio,

In order for this to happen, the property would have to know what external call (SetAll vs. a direct assignment statement) was made to it. This is neither practical nor should it be implemented in this fashion.

Externally, there should be no need to check if the property is protected. If the property is exposed to the outside world, it shouldn't be written to if an interface is provided for it.