> wonder why localhost worked on windows 2000 and not here
There is a big problem with "localhost" it never connects using shared
memory (which is what you want to use when connecting to a local machine. It
only works with TCP and Named Pipes. If these protocols are not enabled
(which is probably what you are seeing here) it will not be able to connect.
In any case you loose a LOT of performance when connecting to a local server
with anything other than shared memory, just don't do it.
For RTM and Everett you should only use :<machine name>, "." and "(local)
when connecting to a local server, never "localhost". This problem is so
rampant that in the current beta1 of Whidbey we are forcing "localhost" to
use shared memory.
--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
I am now blogging about ADO.NET:
http://weblogs.asp.net/angelsb/
"dee" <dee@1> wrote in message news:(E-Mail Removed)...
> wow
> thanks keenan it works ... big life saver
>
> wonder why localhost worked on windows 2000 and not here
> but actually i really care that i can connect
>
> thaaaaaanks
> dee
>
> "Keenan Newton" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Well have you tried getting to the Northwind database via Sql
> > Enterprise manager. If so attempt a query using sql query anaylser
> > once you prove those are fine. Try changing your connection string and
> > instead of pointing the server to localhost, use the actual machine
> > name.
> >
> > SERVER=MyComputer
> >
>
>