I find it better not to use [local} or any reference to the local machine.
It is too easy to deploy an app to a different machine, and now the
reference points to a different machine than it did before. I believe it is
best to use the IP address of the SQL Server, or at least the machine name
(in a LAN).
--
HTH,
Kevin Spencer
Microsoft MVP
Digital Carpenter
A man, a plan, a canal,
a palindrome that has gone to s**t.
"John Timney (MVP)" <x_****@timney.eclipse.co.ukwrote in message
news:us********************@eclipse.net.uk...
I've only ever seen a local connection using (local) and a remote one
using a named server or IP - never using (.). Perhaps the error is a
driver error failing to connect to a db it can't find and reporting it
mistakingly as not being allowed.
Regards
John Timney (MVP)
VISIT MY WEBSITE:
http://www.johntimney.com
"fran" <fr**@discussions.microsoft.comwrote in message
news:8D**********************************@microsof t.com...
>I'm using Sql Server 2005 Enterprise
I have configured it for remote connections.
"John Timney (MVP)" wrote:
>>Are your using SQL Express - have you configured it for remote
connections?
http://www.datamasker.com/SSE2005_NetworkCfg.htm
--
--
Regards
John Timney (MVP)
VISIT MY WEBSITE:
http://www.johntimney.com
"fran" <fr**@discussions.microsoft.comwrote in message
news:29**********************************@micros oft.com...
Hello, there are some difference in a string connection if you use '.'
or
'(local)?
When I use '.' I have the error:
"SQL server does not allow remote connections"
Thanks