Mike Brind said:
Not always a bad idea, but given that it didn't work in this case, it
seems pretty pointless complaining that it didn't work, just as it's
pretty pointless complaining that any official documentation doesn't
explicity exclude all the infinite number of possiblities one could
come up with in terms of incorrect syntax.
First of all, I'm not complaining it didn't work; I explicitly said that I
was hoping for inspiration from the VB documentation but that I accepted its
limitations.
Secondly, I expect reserved terms like 'expressionlist' to be consistent
across MSDN especially since the term 'expression' is not an MS-only term. I
don't expect MSDN to detail the infiinite number of terms of incorrect
syntax, but I would hope it would give a better indication of what is and
isn't allowed. The fact is that I wanted to use a valid expression in the
statement (an expression that MS regard as valid for VB) yet it isn't valid
for VBScript, and on top of that, the most important MSDN help was hidden
because of poor web design, so it was difficult to even infer the right
information. More importantly, I geniunely expected VBScript to be able to
handle this kind of expression, and I'm surprised it doesnt. And I'm
surprised I didnt find any 3rd-party websites that remarked on this
situation - I can't be the first person to hope for more out of the Select
Case statement.
What I would complain about (if it were any use) were the ratio of helpful
responses to those that weren't helpful (like yours). I didn't start this
thread to complain about VBScript - I wanted to find out an answer to
satisfy my curiousity. I eventually got that answer, but not before a number
of people tried to sour the thread with their unhelpful answers. If people
put the same amount of effort into helping posters rather than starting
conflict, this NG would be that much better.
The unintentional insight I gained was that the majority of users seem to be
locked into IE as their preferred UA (which surprised me).
CJM