Or maybe creating an alias with the name « local » (using the Network
Client Utility of SQL-Server 2000, not sure of the translation of the name
here) ?
The real shortcut for the local machine is (local) and not local; so maybe
creating an alias will do the trick.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail:
http://cerbermail.com/?QugbLEWINF
"Cor Ligthert [MVP]" <(E-Mail Removed)> wrote in message
news:%2395xmsz$(E-Mail Removed)...
> Paul,
>
> Did you try to change the machinename and than the server name to "local"
>
> Just a try
>
> Cor
>
> "Paul Robinson" <(E-Mail Removed)>
>
>> Hi,
>>
>> I am having problems connecting to a local SQLServer2000 database using
>> ADO.NET. I am using a 3rd party assembly which I have no control over,
>> and
>> the database connection string is hardcoded into the application (nice).
>> The connection string looks like this:
>>
>> "UID=john;password=johnspassword;Initial Catalog=thedb;Data Source=local"
>>
>> I do have the database setup on the local machine, but when trying to
>> connect I get the error:
>>
>> "SQL Server does not exist or access is denied"
>>
>> Now, I have tried to connect to the database using Query Analyser and it
>> will not connect to a server called "local" but it WILL connect to a
>> server
>> called "(local)".
>>
>> Because I can't change the connection string I need to get it connected
>> using "local". It works on one machine but not the test machine I have.
>> As
>> far as I can tell everything is set up the same.
>>
>> I have tried setting up various aliases for "local" using the SQL Server
>> Client Network Utility, but still having no success. I have set up a
>> named
>> pipe and also a TCP/IP alias for "local" but I still can't get the
>> connection to work.
>>
>> Can anyone help with this?
>>
>> Thanks!
>>
>>
>
>