In my day, before syntax coloring and FoxPro, I had to use all 0's instead of 1's because we couldn't afford 1's. Actually I've been in the comment all or nothing camp since version 1.2. Also, if you don't want to highlight everything you want to comment and then press 'ALT+O' then press 'C', you can simply type * in front of every line you want to comment. If you want to make it look the same way the hot key does it, you can type '*!*' in front of each line you want to comment. If you get tired of typing '*!*' over and over, you can highlight the '*!*' press 'CTRL+C' then place your cursor in front of the next line you want to comment and press 'CTRL+V'. Magically the '*!*' will appear in front of the new line!! Am I annoying anyone other than myself yet??

Sorry everyone, I just find this thread somewhat humorous. It must be a lack of sleep.

>Ah, you know, I never bothered looking up the help on '*' or '&&' before reading your message, because they seemed quite straight forward. Lookie below at what I found:
>
>* Command
>
>Remarks
>
>Place a semicolon (;) at the end of each comment line that continues to a following line.
>
>
>It says right in the docs that it'll do that. I guess then my only remaining beef on the topic is that the syntax coloring doesn't carry over to the following lines to indicate to the programmer that they are indeed NOT going to be executed. At least now I know. Thanks again for your input.