>>I use the same naming convention so it is not a problem for me. I use 'l' to denote a local variable and then the type and finally a descriptive text. Field names are only descriptive text and always referenced with the alias.

Yep- Hungarian Notation became popular just in time for VFP3. But starting in 1995 IME, Remote Views followed by Object scatters removed most of the purpose for variable names matching fields as used to be so common. IME there's also a bell curve of eased maintenance from succinct descriptive naming: when I began, use of "l" as a variable name made sense when your customer's TRS-80 might only have 4K RAM, though you had to survey all the code to understand its use. To this day I try to keep variable labels concise, not least because massive long names are easily to get slightly wrong unless you fossick around and verify, which starts to push the maintenance benefits away again. I think this is less of an issue with static typing and Intellisense or tools like Thor, but old habits die hard. ;-)

Ironically, VFP Compiler obfuscation includes conversion of variables and code sequences into non-descriptive labels and calls that are awful to try to follow, though they do the same things as your original source. Variable names that match field names are one of the few exceptions to survive this obfuscation.