Arthur Fuller
artful at rogers.com
Mon Jul 18 17:31:18 CDT 2005
Thanks! I will give this a try (or rather my client will, and doubtless yell if your suggestions fails LOL). -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Eric Barro Sent: July 18, 2005 2:56 PM To: dba-sqlserver at databaseadvisors.com Subject: RE: [dba-SQLServer] Weird Issue with SQL 2000 Open up your hosts file and add a value for the SQL server like this... Xxx.xxx.xxx.xxx SQLSERVERNAME Where xxx.xxx.xxx.xxx is the IP address In your ADP reference SQLSERVERNAME instead of just (local). -----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 ---------------------------------------------------------------- The information contained in this e-mail message and any file, document, previous e-mail message and/or attachment transmitted herewith is confidential and may be legally privileged. It is intended solely for the private use of the addressee and must not be disclosed to or used by anyone other than the addressee. If you receive this transmission by error, please immediately notify the sender by reply e-mail and destroy the original transmission and its attachments without reading or saving it in any manner. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. E-mail transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of email transmission. Users and employees of the e-mail system are expressly required not to make defamatory statements and not to infringe or authorize any infringement of copyright or any other legal right by email communications. Any such communication is contrary to company policy. The company will not accept any liability in respect of such communication. _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com