>>>No, I think you were reading into that something I didn't mean. Most programmers to something to differentiate between words. CamelCase or an underscore or thisIsMyVariableName (C programmers love that leading letter to be lowercase). I am assuming that some technique will be employed fairly consistently. What I mean was Total should not be seen as a different variable from total. thisIsMyVariableName should be the same as ThisIsMyVariableName. If you want to use all lowercase and run the words together wih no underscore or whatever, then you will get var names that are hard to read, especially with longer ones. On that we agree.
>>
>>
>>OK that is what we would disagree. Total and total being same is a good thing or bad. I say bad, you say good:) Actually it is one of the reasons I like C# over VB.Net. It is a personal adoption to an environment maybe, I like:
>>
>>Book book = new Book();
>>
>>promptly saying to my senses that Book is a class (type in .Net terminology) and the book is a variable of 'type' Book.
>>
>>If VFP was case sensitive I wouldn't even need a PEM editor to see my properties as they should be:)
>>Cetin
>
>PEM Editor does let you preserve case (though you can also do it in plain-old VFP with the right settings), but it does a ton more than that and is a big improvement over the Property window and the Document View window, both of which it is designed to replace.

I downloaded and installed. Doesn't look bad and using in conjunction with the old good PEM window it looks good (I wouldn't agree it is a total replacement).
Cetin