MS SQL Server Clients - SQL Server Express & Access 2000 ADP

Author

SQL Server Express & Access 2000 ADP

Murphy

2006-02-15, 3:24 am

Hi,

I have a legacy db that was run using MSDE with an Access 2K ADP front end,
all worked well.

I now need access to the db again and have downloaded and installed SQL
Server Express, I have also restored my database successfully and can view
the tables using the Studio Express product.

This is all being performed on a local machine however I cannot get the ADP
to connect to the db.

In the ADP when I select the "Connection Properties" the dropdown list of
SQL Servers is empty even after a refresh ?

If I try to connect using osql -E then the following is returned:

C:\>osql -E
[SQL Native Client]Named Pipes Provider: Could not open a connection to SQL
Server [2].
[SQL Native Client]Login timeout expired
[SQL Native Client]An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be caused
by
the fact that under the default settings SQL Server does not allow remote
connections.

C:\>

Any help would be greatly appreciated.

Thanks in advance...

Kent Tegels

2006-02-15, 9:24 am

Hello Murphy,

First on ADPs and SQL 2005: Basically, ADP was really desgined for SQL7/2000.
Given some the changes like the XML Data Type, UDTs and the new LOBs, Microsoft
would have to update a significant amount of code in Access 10 and 11 to
support ADPs for 2005. I suspect there's just not the resources to do that
going forward since the focus is clearly on Office 12. So don't plan on using
them going foward.

Also note that OSQL has been superceded by a new tool command line tool called
SQLCMD.

As to this specific problem: note that when you install SQL Server Express
Edition, it installs into an instance named "SQLExpress" by default. So when
you're trying to use SQLCMD, try

SQLCMD -S .\SQLExpress -E

Thank you,
Kent Tegels
DevelopMentor
http://staff.develop.com/ktegels/

2006-02-16, 9:23 am

Have you checked the network configuration and client configuration
protocals for your instance of SQL Express via the SQL Server
Configuration Manager?

We had to set 'Named Pipes' and 'TCP/IP' from 'Disabled' to 'Enabled'.
I believe these properties have a default value of 'Disabled'.

GG

terra

2006-02-17, 7:25 am

I had the same error message and i solved disabling de windows firewall
I hope this work

"Murphy" <murphy@murphy.com> escribió en el mensaje
news:pxxIf.8378$yK1.3427@news-server.bigpond.net.au...
> Hi,
>
> I have a legacy db that was run using MSDE with an Access 2K ADP front
> end, all worked well.
>
> I now need access to the db again and have downloaded and installed SQL
> Server Express, I have also restored my database successfully and can view
> the tables using the Studio Express product.
>
> This is all being performed on a local machine however I cannot get the
> ADP to connect to the db.
>
> In the ADP when I select the "Connection Properties" the dropdown list of
> SQL Servers is empty even after a refresh ?
>
> If I try to connect using osql -E then the following is returned:
>
> C:\>osql -E
> [SQL Native Client]Named Pipes Provider: Could not open a connection to
> SQL
> Server [2].
> [SQL Native Client]Login timeout expired
> [SQL Native Client]An error has occurred while establishing a connection
> to
> the server. When connecting to SQL Server 2005, this failure may be caused
> by
> the fact that under the default settings SQL Server does not allow remote
> connections.
>
> C:\>
>
> Any help would be greatly appreciated.
>
> Thanks in advance...
>

Sponsored Links