>Terry. I think its Windoze itself. Often I find files named, eg, MyProgram.FXP. I then try to rename to lower case extention, eg MyProgram.fxp. 9/10 times I have to do this twice as the first time doesnt take. Second attempt does. Weird.

I guess its a feature. Sergey's point about a VFP prg crash - and - how VFP automatically services repair by opening the "broken" PRG for view/repair in lower case (I think VFP source is converted to lower case before compile, anyway). When vfp opens the prg, the error management service probably opens the file using a lower case name. That makes sense.

I guess it's a feature. I am still curious as to why an executed PRG OCX will cause the property names in the visual OCX properties sheet to be upper case.

>
>
>
>>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.