>>>Do not use the property sheet in this manner. It is much clearer in code. In the init of the form is the place to set the property.
>>
>>Mike, if properties could be in a not-set state unless their value were set in code, I could agree with you. But that it's not the case.
>>
>>Prefixing an assignment in the properties windows is our way to say to VFP "don't need to be smart, I know what I'm doing and I'm going to assign the value of this property as if if there is no properties window". That is, as if I was writing this in code.
>
>Just because the property sheet allows this, does not mean we should. It is not exactly clear when used.

Mike, that is quite clear and that's how the Properties list is designed. But, of course, I have no problem in admitting that clarity lies in the eye of the beholder.

Quoting:

Properties list

This list shows all properties that can be changed at design time and their current settings. To get Help for a specific property, select the property and press F1.

The property settings in the properties list can appear as follows:
* Property settings that are expressions are prefaced with an equal sign (=).
* Settings for properties, events, and methods that are read-only appear in italics.
* Methods and events display inheritance details as follows:
[etc.]