Thats a fair point Aaron, but I guess I am 'lucky' in that I do in fact have
a W2K server for development. Ok, it's a bit old, but it does the job.
But in answer to Williams point:
There is a hierarchy of machines used in the process. I develop the basic
code on my XP machine. It is uploaded and tested on the development server.
Anomalies are fixed. After enough testing, it is released to one production
server. After user testing, it is rolled out to remaining production
servers. If I were to use the development server for all my development
work, I would cause a lot of inconvenience/problems for the other developers
who share the server, hence XP is used in the first instance.
After a bit of head scratching I did finally find the answer on our
development server...
But my point still stands. I'm surprised it doesnt appear in IIS5.1. This
*is* a genuine web server and there is no reason why this ODBC feature
couldnt have been included.
I'm sure His Royal Billness had his reasons for this, but it's academic -
things are the way they are. Its only a minor inconvenience anyway.
Cheers
Chris
"Aaron Bertrand - MVP" <aa***@TRASHaspfaq.com> wrote in message
news:eP**************@TK2MSFTNGP11.phx.gbl...
[snip]
Granted, not everyone can afford to license Windows Server 2003 on their
day-to-day desktop. Even with a proper MSDN license, there's a fine line
between "development and testing" and "business use."