I dislike this "feature" very much. I'm wondering, if there is a way to automatically preserve proper name after changing? Right now I had to go to Explorer and do re-naming myself.

I guess, there could be some reference file or table with correct names and WSH can help in handling renaming back... Just an idea for the future...

>In my retentive, meticulous approcah to project management, I sometimes go to extremes. For example, I apply a proper case convention to PRG names, so that they appear in Explorer or the Open() dialog with a mix of upper and lower case characters.
>
>For example: MYProgram.PRG
>
>The programs are opened through command window (modi comm MyProgram) with the case conventions, or through the open dialog (in which case the offer list presents available PRGs in proper case).
>
>Despite this effort, some programs (especially those responsible for a crash or memory leak - usually the PRGs crashing due to coding or logic error inside ActiveX methods or classes), re-appear - after the crash in lower case.
>
>Why is that? Is it by design to let me know "this program recently crashed"
>
>Also - when working with the properties sheet to review a visual list of an ActiveX controls properties, if a routine that preceded the "visual" inspection used PRG activex, the properties that were set in the PRG class (of the preceding routine) appear in UPPER case.
>
>Just courious if these are features. If so, then they are useful because they highlight an issue. If so they are a very clever and subtle layer to the VFP development environment. If so - it would be interesting to understand the story behind the story, and understand how MS engineers came to include this "feature" in VFP.