your experience is very limited.
Touché <g>! Notice this is the 'getting started' group i.e. I think
you should assume everyone here has very limited experience. Your words
could be perceived as being rude: if you genuinely believe me to be
inexperienced then you are rubbing it in my face; if you suspect I am
experienced then you are being sarcastic. However, because I'm a
considerate person, I'll give you the benefit of the doubt and assume
you didn't mean your comment pejoratively. We're cool, dude ;-)
if we limit it to programming and exclude medical and legal
procedures
Yes, the context is important. I'd think nothing of a plea for
'relationship help' or announcement of a 'backend problem' if the
newsgroup in question was an Access one (beyond a small titter,
naturally).
VBA Subs and Fuctions [sic] are both procedures.
In VBA terms, 'procedure' on its own is vague. I would expect
consensus on the Sub and Function keywords pertaining to 'sub
procedure', though.
Unlike VBA, SQL has a PROCEDURE keyword and the regulars round here
don't respond well to the industry-standard term 'stored procedure'.
The ghettoised 'parameter query' doesn't translate well when the
PROCEDURE in question could contain a SQL *statement*
(INSERT/UPDATE/DELETE), rather than a query.
BTW I tend to quote SQL keywords in uppercase, at the risk of appearing
as though I am shouting. If everyone was as considerate there would be
little room for confusion over terms such as PROCEDURE.
Jamie.