I'm currently working in an .mdb file on my laptop and trying to link to a
table that resides in a SQL Server 2000 "Personal Edition" database on my
desktop. I've tried creating a variety of ODBC System Data Sources on my
laptop, as well as checked the server's network/security settings and still
can't establish a connection. Will SQL Server 2000 "Personal Edition" allow
a remote connection or is it for local use only? Any guidance is much
appreciated!

I assumed you meant the MSDE 2000?

I have an MSDE 2000 installed on my PC for testing and I have been able to
connect to the MSDE remotely using TCP/IP. My guess is that Named Pipe
should be fine also but you need to check your MSDE set-up to see whether it
is configured for Named Pipe or MSDE or both.

Have you been able to set up a ODBC DSN on the computer where the MSDE is
installed?

--
HTH
Van T. Dinh
MVP (Access)



"RHamilton" <(E-Mail Removed)> wrote in message
news38E6E55-45BF-41D0-9A19-(E-Mail Removed)...
> I'm currently working in an .mdb file on my laptop and trying to link to a
> table that resides in a SQL Server 2000 "Personal Edition" database on my
> desktop. I've tried creating a variety of ODBC System Data Sources on my
> laptop, as well as checked the server's network/security settings and
> still
> can't establish a connection. Will SQL Server 2000 "Personal Edition"
> allow
> a remote connection or is it for local use only? Any guidance is much
> appreciated!

Thanks for the quick response! Personal Edition is a version SQL Server 2000
that came with Office XP Developer Edition. It's a step up from MSDE in that
it includes all of the utilities (Enterprise Manager, Client Network Utility,
etc). I have been able to create a system DSN on the desktop and link a
local .mdb to the local SQL database. The problem arises when I attempt to
create a system DSN on my laptop that references the SQL Server on my
desktop. I'm able to see the desktop in the list of servers. However, after
clicking "Next", I receive a "Login failed for user 'Servername\guest'."
Named Pipes and TCP/IP are both enabled in the SQL Server. Thanks again for
your response.

"Van T. Dinh" wrote:

> I assumed you meant the MSDE 2000?
>
> I have an MSDE 2000 installed on my PC for testing and I have been able to
> connect to the MSDE remotely using TCP/IP. My guess is that Named Pipe
> should be fine also but you need to check your MSDE set-up to see whether it
> is configured for Named Pipe or MSDE or both.
>
> Have you been able to set up a ODBC DSN on the computer where the MSDE is
> installed?
>
> --
> HTH
> Van T. Dinh
> MVP (Access)
>
>
>
> "RHamilton" <(E-Mail Removed)> wrote in message
> news38E6E55-45BF-41D0-9A19-(E-Mail Removed)...
> > I'm currently working in an .mdb file on my laptop and trying to link to a
> > table that resides in a SQL Server 2000 "Personal Edition" database on my
> > desktop. I've tried creating a variety of ODBC System Data Sources on my
> > laptop, as well as checked the server's network/security settings and
> > still
> > can't establish a connection. Will SQL Server 2000 "Personal Edition"
> > allow
> > a remote connection or is it for local use only? Any guidance is much
> > appreciated!
>
>
>