>>>>- People used total unreadable variable names (like ldInvDte).
>>>
>>>Well, I wouldn't say that was unreadable - I take it immediately to be local date Invoice Date field, but, I agree with you that lazy-arsed var names should result in the shooting at dawn of the programmer. Just the inclusion of one letter, "a" would have made that amply readable.
>>
>>Not enough. ldInvDate is what - invoice date, inventory date, invention date or inversion date?
>
>Granted. As I already said, there's no excuse for lazy, truncated var names. But, we're back to context again, D; I think the programmer would know if he was editing an Invoice, inventory or Invention system, don't you?

Invoice and inventory can both influence a warehousing app... and I'm still cursing myself for not foreseeing that my app will include an inventory... so I have something like bzInv...prg which is handling invoices, and then I had to give fuller names to bzInvtory...prg so I'd know which is used for what. Specially when going down the project and its flat list of files. Sometimes I wish I had the time to write a better interface for VFP projects, like grouping related stuff into a treeviewlike structure. Nowadays, I have to have longish filenames just to keep the related pieces together. Three prefixes if needed.