>Agree. When I created this property originally lDontPerformValidationOnClose sounded just right <g>, but today when someone asked me about the behavior and we looked into this property with my colleague, it stroke us both as quite odd <g>
>
>I've already changed it to lValidateOnClose and updated the code. By using Code Reference I found, that I used this property only once in the project so far...

Code Reference is, as they say, like sex: those who didn't try it don't know what all the fuss is about, and those who did can't imagine how did they live without it :).

I catch myself often thinking of "dang, who knows in how many places are we using this... if I change it, what may happen?". And then I remember Code References, and find it in a minute - extremely cool. I know there are other tools, like GoFish or simple file search (not Windows file search - I mean TotalCommander), but CR has a great advantage from its integration with code editors: you just doubleclick it and it opens at exactly the spot where it found the string. You can refresh your memory right away.

Sometimes I catch myself opening CR more often than the debugger :).