This is only a requirement for the "user who wants to use the MMC snapin".
Now you could use the object model and specify everything there, not using
the UI at all. Then you don't need the SQL client setup.
Also, in the future, when we move away from "sql only", this requirement
will change. For now it's the "laziest" way to find all SQL servers on the
> Installing the SQL Server Client Setup did the trick. Thanks for the
> Is this only a requirement for the technology preview? I'd like to have a
> thin client approach and deploy client-side ASP -- only requiring IE 5.0.
> > Did you install :
> > a) the admin pack on that workstation ? The registration tool needs the
> > admin dlls installed (and by default, they are not installed on W2K
> > workstation)... I guess you did, otherwise the tool would not work in
> > first place...
> > b) did you install the sql server client setup on the workstation ? We
> > using currently the sql server objects to test the connection etc, and
> > are installed with the sql server client setup...
> > Please let me know.
> > Regards
> > Frank Mantek
> > Microsoft
> > > I am running Windows 2000 advanced server (with SQL Server 7.0) and
> > Windows
> > > 2000 professional client. FYI, the registration tool succeeds from
> > > server but on the client, is never able to see my SQL Server (does not
> > show
> > > up in the combo box and I get an error suggesting my 'sa' login is
> > if
> > > I type in my server name).
> > > Thanks,
> > > Phillip