Jim Lawrence
accessd at shaw.ca
Tue Jul 19 01:31:39 CDT 2005
Hi Arthur: Not knowing the details of the issues I will have to start asking the basic question like: 1. The server is named and assuming that a remote the computer on which the remote SQL resides has a unique ip address/domain name? 2. Your domain server can be pinged? Ie. Ping MyAlias.MyDomain.com 3. Your SQL server is using the default port or/and that is specified in the connection string? (1433) 4. The connection capabilities has been shut down due to some firewall (software/hardware) on your client's site? 5. Have him manually enter the connection string in the EM. i.e. MyAlias.MyDomain.com. He will then need the appropriate Username and password to complete the connection. 6 The connection string could be something like: "Provider=SQLOLEDB;Data Source=MyAlias.MyDomain.com,1433; Network Library=DBMSSOCN;Initial Catalog=MyDatabase;User ID=MyUsername;Password=MyPassword;" (Assuming ADO-OLE and your connection port is 1433) HTH Jim -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Monday, July 18, 2005 11:27 AM To: dba-sqlserver at databaseadvisors.com Subject: [dba-SQLServer] Weird Issue with SQL 2000 I am doing work for a client, whose current SQL 2000 install is on his notebook. The real-world app uses MDB format, until we get it shaken down and all the insects (or most) are purged. My db-server is called Rock. His has another name. It reduces to (local) since it is on his notebook. I build an ADP that talks to the db on Rock. I send it to him. He opens Enterprise Manager and can see only the actual name of his notebook (some bizarre name assigned by Dell, consisting of "PC" plus a bunch of digits). I have two problems. 1. I ship him the latest ADP, which connects to Rock (my server). It won't work on his box unless and until he re-assigns the database server. That's as expected. He can open the server in EM and visit all the tables. When running the ADP, he can interrupt its open, then choose File | Connection... but then cannot enter local or (local) as the server name. I give him a backup of my DB, install it using EM... and still Access cannot see the server (which is the local box). 2. I renamed one of my boxes that hosts SQL 2000 to the same name as his box. Strangely enough, I now cannot see this box or its SQL instance from my development box. Prior to the rename, I could see this box just fine. I have rebooted several times in hopes that the new electrons might cure the blindness, but no such luck. I would like either of the following to work: a) I devise a recipe for him to change the connection details so the ADP can talk to his box (local). b) I revise whatever definitions on my newly-renamed box that I need to revise, so that i) I can see said box from my development box, and ii) the resulting ADP can be copied to the client's box with no edits. I have not suffered this problem before, and I am quite unable to deduce why I am now suffering it. Advice appreciated much! Arthur _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com