>>Hi George,
>>
>>What about other developers that have to modify your code?
>>
>Tracy,
>
>That's one of the reasons why it should be well documented. Not only in terms of a "Programmer's Reference", but also the structure of the code itself.
>
>The methods should be self-documenting and the comments should tell the why, not the how.
>
>One more thing that helps is UML diagrams.

I think more than 'code', George...

It sure can be helpful to use the description field of DBC-resident table fields, as well as comments re the table itself.

Same goes for user defined properties and methods.

This all takes a little longer while 'coding' but it sure can help the new maintenance guy, as well as keep him/her off your back.

cheers