>>>>Muchas gracias de nuevo. I always have a CATCH even if sometimes I have no code there. The purpose is to simply suppress the error.
>>>
>>>Comment is code. I usually have at least one line where I'm explaining why I'm not doing anything there, so someone else after me wouldn't be tempted to invoke app shutdown for an ignorable error - e.g. something optional.
>>
>>Actually I do have a line of comment too. But I am not sure that anybody after me will ever read this line :(.
>
>These can be precious, though. I took care to date my comments (an intellisense script does that nowadays, using datetime() and sys(0)), so I'd have at least some context for myself.
>
>The best example for that I had in, I guess, 1993, when I was asked by a customer to add the rebate option to one of their special kinds of invoices (and they were all special :). I immediately remembered that I asked three years before that whether the rebate is taken off before or after tax (I know the latter doesn't make sense, but hey, I've seen that applied and I knew why I was asking). Pulled up the source, and there it was, the comment in the place where rebate should have been calculated, saying "* 23.06.1990 {guy's name here} said that mill invoices will never have a rebate". Just showed the line to the guy and he said "I know, I know...".

The only good thing I can say about my comments is that when I look at some that I wrote years ago I want to break the hands of the person who wrote them <g>.