Oy vey.

[azurelunatic]

Does anyone know how, before I wander home, to comment code in MS Access variety SQL?

Comments

[silmarian.livejournal.com]

I"m not sure you can. Access is designed to be used by people too dumb to touch the code. :b

[spacemummy.livejournal.com]

Mwahaha!

[azurelunatic]

::whine::

...but-but-but... I'm s'posed to *comment* my labrynthine code so I'll know what it *does* when I go back to *edit* it!!

Seriously, it gives me the heebie-jeebies to write code that I know is evil and then not be able to pick it apart bit by bit and label it.

Ron would be proud of me.

[boojum.livejournal.com]

I'm glad you said that. I will not categorically claim that all lack-of-commenting is evil, because I have heard things from trustworthy people about Extreme Programming which suggest it might be possible, given whole rafts of other stuff, for comments to be extraneous and even somewhat unhelpful. In the general case though, commenting is good, and people who don't want to comment should be shot.

I liked the CS assignment of "Here's this code. Fix the bugs and make it also do x, y, and z. Oh, and since we're being nice to you, we advise you to make it legible first." Legible code much much much much nicer for maintenance purposes.

I think the garden-variety SQL comment is something weird. Have you tried a comma, a colon, or a semicolon as a beginning-of-line comment? Failing that, MS seems to have decent online documentation. Google can be told to restrict its search to a certain site, so searching their Access site for "comment delimiter" or something might work.

A very lackadaisical googling also suggests the hash mark as a beginning-of-line comment marker in Microsoft SQL only. I'm beginning to be fried from the cold, so I can't do a trustworthy-check on the source.

[azurelunatic]

I will try things. We shall see.

[azurelunatic]

As soon as my brain recovers from the happy antisnot chemicals.

[azurelunatic]

The teacher didn't know a way...