ADP freezes when it can't find SQL Server

[LisB]

I have two issues that are probably related: First, none of the
connection strings for my adps work anymore when trying to connect to
the local server via the name, like ServerName. Instead I have to use
the IP address. When I went to test connectivity via an ODBC
connection, I discovered that the name of my local server shows up 3
times in the dropdown list to choose a server. I don't know how to fix
this and suspect this is what is causing the problem.

Second, I have one ADP file that will not open at all. It just freezes
so I can't get in there to change the connection string. I need to
somehow change the connection string without opening the file. I found
an earlier post on this issue:
http://groups.google.com/group/micr...81962c0dc0e?lnk=st&q=&rnum=7#4285281962c0dc0e
about using a hex editor to change a property in the ADP file, but I
couldn't find that property, and am fairly clueless about using a hex
editor.

If anyone has any advice on how to open this ADP file or figure out
what is causing my local SQL Server name resolution not to work
anymore, I would greatly appreciate it.

I tried creating a new ADP file and then importing the objects from the
one that freezes up, but that just froze up also.

Thanks.

Lis B.

 

[Sylvain Lafontaine]

ODBC is well known for duplicating server values; however, this should be a
problem for you because ADP use OLEDB, not ODBC.

If you have access to the SQL client tools on the local machine, then use
the SQL-Server Client Network Utility to enable TCP/IP and Named Pipes only
and clean on the Alias tab any unneeded server alias:

C:\WINDOWS\SYSTEM32\CLICONFG.EXE

As to your current problem, it is possible that a firewall is blocking the
named pipes over the network or that the Multiprotocol is doing its usual
share of problems; however, using TCP/IP instead of a named pipe will give
you a better performance.

 

[Sylvain Lafontaine]

For your second problem, open Access but without opening any file (either
MDB or ADP) and then from it, try compacting and repairing the ADP to a new
file. Maybe this will help.

The fact that you cannot make any importation is an indication that maybe
the ADP file is now corrupt.

 

[Sylvain Lafontaine]

Sorry: « ODBC is well known for duplicating server values; however, this
should *not* be a
problem for you because ADP use OLEDB, not ODBC. »

 

[LisB]

Thank you very much, Sylvain. Cleaning the Alias tab seemed to fix
both problems. I hadn't realized I could compact and repair a database
into a new database. Now both the new one and the old one open since I
no longer need to use the IP address as the server name. I much
appreciate you making my day easier!

Lis B

 

[aaron.kempf]

northwindCS.adp or northwind.adp has a nice example for elegantly
handling situations where you can't see the server
copy and paste

-Aaron

 

[brucek]

Aaron, for some reason I don't have those northwind.adp files on my
machine. Do you know if I can download them from Microsoft somewhere
or do I have to install them from a Access installation cd?

thanks,
Bruce

 

[aaron.kempf]

did you do a find file for northw*.adp?

it's either in a default office installation; or on the office / acces
disc.


Open NorthwindCS.adp from its default location: Program Files\Microsoft
Office\Office10\Samples for Access 2002, and Program Files\Microsoft
Office\Office11\Samples for Access 2003.