From a practical standpoint, I have seen the most risk in using reserved words when adding custom properties or methods to objects when those names are valid property or method names for other vfp objects. Adding a FontBold prop to an object based on the Control class would be an example, as this is a valid prop name for other classes.

>Thanks Jim ! Now it is much more clear for me. I must say that I have no problems with using reserved word as a name. I just try do not use such words as name (with two exception refresh and release) so I don't have problems with them. As regards as VFP behaviour for me it is OK. I think that a sentence in VFP help like "use reserved words on your own risk" or "use and enyoy" or "now you can use but in future it can change" or similar would be enough.
>
>
>>Current behavior is this: "quietly let use the word as a property name"
>>
>>Either of these would be an enhancement request:
>>- should generate warning about using reserved word and let use the word as a property name.
>>- should generate error message and do not let use the word as a property name
>>
>>
>>I think the warning idea has some merit. You could post this over to the VFP Wish List.