>>>>>Are you using naming that reuses identifiers by changing case? Have you run out of all possible alphanumeric combinations or what?
>>>
>>>I do this routinely to simplify remembering form and report names:
>>>FrmCustomer frmCustomer = new FrmCustomer();
>>>
>>>Is that frowned upon?
>>
>>Nope, that's precisely what is best practice in naming conventions... You can tell immediately from the casing what the scope of the variable is...
>
>
>In C# the scope of a variable isn't an issue for me as all my variables are private and any data I want exposed is done through properties. Even in VFP I coded this way, I always defined my variables private, so there was never an reason to put a scope identifier on a variable name.

they can be private but still be scoped global to a class and its related methods..