generally folks comment in their stored procedures, or in their code.
I've never heard of a comment inside an sql statement. not sure I would vote for that.
> Why not? it would be nice to have.
>
[quoted text clipped - 5 lines]
>>> i want to know how i can have some text commented with in Sql
>>> statement,
A saved parameter query is Jet's equivalent of a stored procedure. I will
not debate whether it fits your definition of "stored procedure". One
executes it from ADO the same way one executes a SQL strored procedure. One
adds/modifies it in ADOX using the Procedures collection, the same way a SQL
stored procedure is maintained using ADOX
I am assuming the OP is talking about a saved query, and not an ad hoc sql
statement being built in his script. In the latter case, the comments of
course should go in the script. In the former, the Description property
works well.
I have an old Access aplication with hundreds of saved queries in it. It
would be impossible to maintain that application today if I had not utilized
the Description property to store comments about the saved queries.
> generally folks comment in their stored procedures, or in their code.
>
[quoted text clipped - 16 lines]
>> header is my spam trap, so I don't check it very often. You will get
>> a quicker response by posting to the newsgroup.

Signature
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
Jon Paal [MSMD] - 22 Jun 2007 18:48 GMT
seems the OP has been the only one not participating here...
Bob Barrows [MVP] - 22 Jun 2007 18:56 GMT
> seems the OP has been the only one not participating here...
:-)
True

Signature
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"