The framework I use, Visual Extend, saves preferences (separately by user and form) using the .Name property, so I try to make it unique.
Otherwise, if you don't use this property in code, I see no problem with duplicates. For example, the management of multiple open forms would typically be done through the forms array, i.e. an array, stored in a property of the application object.
>VFP form has property NAME that is displayed in the caption of the Form Designer.
>When a new form is saved, we assign a file name like MYFORM.scx.
>The form is referred in codes by the file name.
>
>Where the form.name is used?
>I have to make some changes in an application and found that several forms have the same property name. To leave it as it is now or to change forms names?
>
>Thanks
>
>Ed
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
