I’m a bit of an obsessive commenter in my own code, I not what my variables are used for, what this block of code does, the point of it being there, and anything I intend to add/edit in the future.

When I remove a block of code, I put in a comment to explain what I used to do, and why I made the change, along with the date. If it’s something I may consider going back to later, then I’ll have a backup copy saved somewhere that will have that code if I should have need to access it at a later date. If I removed the code because it didn’t work or was way more effort that actually required (like I found an easier, more effective method) then I may or may not have a backup copy of it lying around, but that will be noted in the comments as well.

Solid comments can make your code go a long way towards helping other programmers understand your code, and it helps you out too if you come back to a report after several months/years and have to remember what in the world you were doing. I’m not a VFP programmer either, so a lot of this stuff is beyond Greek to me, save for where it shares similar syntax with VB.

1. It would take a little time and effort.

2. The code would be easier to understand making customers less likely to pay M2M for customizations.

It would be nice if one or more customers/users would go through all the programs, clean them up and then distrubute the code to the customer base. But that would take a lot of time and it really should be M2M’s job, not ambitious customers. Not being much of a VFP programer, I would really appreciate it if there were a lot more comments explaining what the code was doing and why.